Due for release soon Pages - add support for pages which do not use suite wrapper

[Nathan Explosion]

First time this one has come up - a page (containing a database) which is configured to not use the suite wrapper will not load the following items:

• JS file
• data-controller for the JS to be called.

As a result, adding the translation template to the database listing template will simply present the menu but clicking an item in the menu will have no effect as the underlying JS code isn't there to action the request.

Likely method to use to assist with this will be:

• add a check in the 'Menu' extension that determines if the page is using the wrapper
• If it is, load the JS the normal way
• If it isn't, load the JS a different way (likely load a template)

Functionality will be in (NE) Content Translator, not back-ported to (NE) Translate

[Nathan Explosion]

 

 

[Nathan Explosion]

I am hoping to have "(NE) Content Translator" released end of next week - I have next week off from work, and hoping to spend more time finishing off the testing on a few outstanding items ahead of a new release.

As per the listing for "(NE) Translate", existing customers will be automatically provided a purchase of the new version upon release, at the same renewal terms at which they purchased the original resource.