How can I stop the "_edit" suffix being added to all the links in my simple edit pages?
Essentially - this would cause the user to exit the edit mode if they click on any link on the screen outside the editing areas.
A related question - how can I specify a different design for simple edit pages?
At the moment this isn't possible. You can, however, use a different design. You build the design switching code into a link that is being generated on the page, so clicking on the link will take you into simple edit mode as well as flipping the design. You need to setup 'user defined designs' with unique names so they can be called from the query string in the url.
Something else that we've been working on is presenting the edit screen in an Iframe with a design that only shows the body content. That way you can keep your normal navigation in your design (clicking on a normal url will cancel simple edit), and have the edit screen still appear in context of the page you are editing.
[quote]You can, however, use a different design. You build the design switching code into a link that is being generated on the page, so clicking on the link will take you into simple edit mode as well as flipping the design.
[right][post=“7120”]<{POST_SNAPBACK}>[/post][/right][/quote]
I’ve implemented this on a site (Matrix 3.4.3) and it appears to be buggy. The _edit JS and CSS aren’t added to the page so it breaks. I’m also using it in combination with a layout.
Bug raised in the bugtracker.
Can you post the URL you are using to flip the design and enter edit mode?
[quote]Can you post the URL you are using to flip the design and enter edit mode?
[right][post=“7375”]<{POST_SNAPBACK}>[/post][/right][/quote]
I’ve PM’ed you Anthony - it’s a project in development, thus cloaked, but it’s on a squiz uk server.
Thanks Sam. replied to your message. The URL itself appears to be fine. I think we may have to get a member to check this out on your server more thoroughly, this shouldn't be happening. I'm wondering whether it may be a version problem that has been resolved in later releases. We use this extensively in a client system here in Canberra both in 3.4.5 and 3.4.6 systems and it keeps the proper javascript in place.
[quote]We use this extensively in a client system here in Canberra both in 3.4.5 and 3.4.6 systems and it keeps the proper javascript in place.
[right][post=“7395”]<{POST_SNAPBACK}>[/post][/right][/quote]
Yes, I too (as did squiz UK) suspect this is an issue with v3.4.3. I’ve reverted to the standard design template for the moment.