You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempting to edit a Site asset via an /_edit URL results in a redirection to the site's index page, and there are no other ways to prevent this redirection taking place.
The JavaScript code that is present within easyedit.min.js (obfuscated, so impossible to reference a line number; grep for EasyEdit.redirect) in certain locations (page load, Asset Map) attempts to load the asset_index_id for the current asset. On successfully retrieving a valid asset ID, the JS performs an EasyEdit.redirect() call, which 'redirects' user.
A solution is to either don't redirect to the index page (eg people can get to an index page via the Asset Map anyway), or provide a clear/documented way of getting to Edit+ for a site (specific URL, request argument etc) to disable this behaviour. With regards to Asset Maps, trying to access your Site asset should always edit the site asset.
The text was updated successfully, but these errors were encountered:
My workaround is to inject code into the Squiz_Matrix_API call for getting keyword replacements that tracks if anyone is asking for asset_index_id. If this is seen, then change the replacement to something that doesn't exist and run the 'replacement'. This essentially disables the redirection and allows users to correctly edit a Site. Users visiting the edit interface can still easily get to modify the index page, plus I provide a front end link to do so.
This is also related to Edit+ users not being able to configure Index/Not Found assets. With the issue fixed above, these have been added into the Edit+ interface.
Attempting to edit a Site asset via an /_edit URL results in a redirection to the site's index page, and there are no other ways to prevent this redirection taking place.
The JavaScript code that is present within easyedit.min.js (obfuscated, so impossible to reference a line number; grep for EasyEdit.redirect) in certain locations (page load, Asset Map) attempts to load the
asset_index_id
for the current asset. On successfully retrieving a valid asset ID, the JS performs an EasyEdit.redirect() call, which 'redirects' user.A solution is to either don't redirect to the index page (eg people can get to an index page via the Asset Map anyway), or provide a clear/documented way of getting to Edit+ for a site (specific URL, request argument etc) to disable this behaviour. With regards to Asset Maps, trying to access your Site asset should always edit the site asset.
The text was updated successfully, but these errors were encountered: