Here is the latest update with this:
----------------------------------
Bug 1 - Translate service run in step throws exception
The Translate services are throwing exceptions when I run in step and load from the UI with desktop view
This is probably unrelated though because when I ran it from the site, I still got the text and there is no exception. This limits my testing so having to actually create an order each time though instead of running in step so I'd still appreciate some attention to it.
I might be missing something. Im just running the existing code in step which I think used to work. It doesnt have any variables inside the service
----------------------------------
As for the issue from my last post, where it would translate alright but the link would not work, we found in a call with the internal team that the html had CDATA everywhere and a comment at the top from the previous developer:
"Wrapped entire thing in CDATA so EP likes it"
I undid this to see what EP didn't like about it and found it:
So all over where it has some html tag with a reference for an image or url that is set to an xsl value of, I had to put that in a previous CreateServiceNode to create the html and reference that in the final html
But this solution treats my 2 scenarios differently.
Here it is after the createservicenode is ran for the footer image which is only an img tag:
Here it is after the createservicenode is ran for the facebook logo. This is an a tag with a span and img tag inside of it:
Bug 2 - Cant get social media icons to display on page
Here is how I reference it in the html (with a /* in the xpath):
And here is how it ends up after the datasource logs:
and on the page, it doesnt show the logos at all:
- image.png (1.03 KiB) Viewed 2992 times
- image.png (1.03 KiB) Viewed 2992 times
(this says "follow us on", and it should have the logos right next to it)
And if I change it to a /. in the xpath, here is how it ends up in the datasource logs:
and on the page, it shows that html on the page:
The footer image is working now though! So it seems the fix should be somehow to get the CreateServiceNode to output the facebook html the way it is outputting the footer image (still as xml)