One issue : links to documents and images inserted into the RTE via macros don't appear to be picked up by Nexu, allowing editors to delete said media items with no warning. Is this something that could be addressed?
Thanks for the prompt response and I take your point re. the RTE and macros.
(Our current approach to preventing inadvertent deletion is rather brute-force. We search 'cmsPropertyData' for the id of an item being deleted and as our macros generate un-parsed content in the RTE containing the item id, they get picked up. The approach gives no false negatives but some false positives where an item id being checked may be a legitimate non-id value within a property. Very inelegant in comparison to Nexu!)
Have just been reading the Nexu docs relating to adding new parsers! This looks very promising: we can identify defining text in each of our macro-based inserts that could be used in a similar way to the default implementation of the RTE parser.
Media Items Inserted Into RTE Via Macros?
Hi Dave,
Great plugin by the way!
One issue : links to documents and images inserted into the RTE via macros don't appear to be picked up by Nexu, allowing editors to delete said media items with no warning. Is this something that could be addressed?
Thanks,
A
Hi Angus,
Don't think this will be possible. The output of the macro is not stored in the RTE. So there is no way to find out what it is referencing.
I actually never use macro's in the RTE. IMHO opinion there are better options, e.g. grid, nested content, .... to let editors build dynamic pages.
Dave
Hi Dave,
Thanks for the prompt response and I take your point re. the RTE and macros.
(Our current approach to preventing inadvertent deletion is rather brute-force. We search 'cmsPropertyData' for the id of an item being deleted and as our macros generate un-parsed content in the RTE containing the item id, they get picked up. The approach gives no false negatives but some false positives where an item id being checked may be a legitimate non-id value within a property. Very inelegant in comparison to Nexu!)
Thanks,
A
Hi Angus,
You can always override how the RTE is parsed by adding your own parser that supports macros
dave
Hi Dave,
Have just been reading the Nexu docs relating to adding new parsers! This looks very promising: we can identify defining text in each of our macro-based inserts that could be used in a similar way to the default implementation of the RTE parser.
Thanks for your help,
A
Nice would love to see what you come up with.
Dave
is working on a reply...