With the advent of SDL Web 8.5, we’ve seen many nice improvements to the software. We’re able to move items in the blueprint hierarchy, we can now set up a whole content delivery environment with a number of powershell scripts, … but in our most recent upgrade, we’ve found a big problem.
I’ve been keeping a little notepad file on my machine for a while some of common code snippets that help when building SDL Tridion Gui / Alchemy extensions. I thought it would be great to share them with the community in the hope that they can help someone, and others can contribute.
Last week I had the pleasure to attend SDL Connect as a guest, speaker and sponsor. My presentation was focused on creating a Technical Strategy for Customer Experience (CXM).
So why another MVP blog?
I promised myself I’d put something together after my first MVP Retreat but it’s taken me a while to ‘get over it’ (this is, of course, a reference to the amount of food that was eaten).
We recently worked with one our customers looking to implement personalization within their SDL Tridion environment. The client was looking to use either SDL’s Experience Optimization (XO)* or Adobe’s Target product.
We had a scenario while building a form on Java DXA 1.7 and tried to have it submit via POST, not GET. We had the form working perfectly via GET, but when we changed the method to POST the response was a 403 Forbidden. We poked in many directions, such as directory security settings and web.xml configs. In the end it was the CSRF configuration built into DXA that was the answer…
This years SDL Tridion User Group in Ohio is a wrap. SDL came to present their road map for the Tridion platform. I presented some updates to Alchemy and a number of plugins that are under development.
Why was it different this year (TDS2017)? And why should I go next year?
This year, as ever, was a festival of information packed presentations with lots of opportunities to network with developers and some customers too. Not only that – Content Bloom were the Diamond Sponsors so it was great to have a strong contingent from our various offices across the globe (including Nova Scotia, New Orleans, Belgium, UK, India, Czech Republic, Ukraine).
DXA is a reference Tridion implementation that contains tons of pre-configured rules and automated features. These features reduce the time to market for simple Tridion-backed websites. However, there are a few “features” in DXA which are not defined in the documentation and may not be desirable for all sites. One of these “features” is the fact that DXA will crop any image rendered in an RTF to the Golden Ratio of 1.62.
So I finally got around to having enough time to set up a Java-based DXA connecting to a Content Service in the Amazon cloud.
It was a fun adventure, to say the least, and most of it is due to my rustiness in Java. I have tried with both Eclipse and IntelliJ Idea, and definitely IntelliJ made it a lot simpler by detecting project dependencies and installing them for me – which actually made it harder to get Eclipse to work, as I hadn’t noticed what it had done.
Anyway – below are the steps I followed to get a local instance of DXA running within Eclipse. As with the .NET install, you need to make sure you have a proper firewall configuration allowing communication between your machine and the CIS, as well as having the right mappings set in Topology Manager (I used the default of “localhost:8080″ for this). I will not cover those steps in this post.