SC Publish Redirect
Developer
3rd Party (Free)
422 downloads (last 90 days)

EE Version Support
- ExpressionEngine 2
Compatibility
If an item is crossed out, it might be untested, not applicable or incompatible. Contact the developer to be sure.
- Updater
- Multi Site Manager
- Stand Alone Entry Form
- Low Variables
- Content Elements
- Better Workflow
- Matrix
- Grid
- Webservice
- Publisher
Requirements
- jQuery for the Control Panel
Add-On Type(s)
Extension
Tags
Publish Redirect is an ExpressionEngine 2.x extension which allows you to redirect a user to a specific page after updating or adding an entry. By default the extension will redirect the user back to the current entry edit screen and display a message.
Please not that this extension uses the “entry_submission_redirect” hook.
Installation
- Download the extension from GitHub
- Copy the /third_party/sc_publish_redirect directory into your /system/expressionengine/third_party/ directory.
- Login to your EE Control Panel.
- Go to Add-ons > Extensions and enable the sc_publish_redirect extension.
Changelog
Version 1.0.1 2010-11-04
- Changed priority for extension because it conflicted with Structure Module
Version 1.0 20100111
- Initial public release
Settings
Once installed, there are a few settings that you might like to play with. By default, once the extension has been enabled, anytime you Publish, or Edit an entry, when you click the “Save” button, it will return you to the entry edit screen.
Select a redirect option
Select one of the following from the drop down list:
- Redirect back to entry [default option - returns you to the entry editing screen]
- Redirect to edit list [returns you to the Edit Channel Entries page]
- Redirect to publish screen [opens a new publish screen]
- Custom URL
Custom redirect URL
This field is ignored unless you have selected “Custom URL” from the drop-down list above. Simply enter any URL in here, and it will redirect to that screen (i.e. if you want it to redirect to the Apple site after saving an entry enter in http://www.apple.com/ ).
Note with this setting you can also use the following variables:
{base} - your site’s URL
{entry_id} - the entry_id of the saved entry
{channel_id} - the channel_id of the saved entry
So therefore you can create custom URLs that redirect to specific places in your CP. For example, to return to an empty publish page for the same channel as your saved entry, you would enter -
{base}&D=cp&C=content_publish&M=entry_form&channel_id={channel_id}
Success message
This simply lets you set a custom message to tell users the entry has been saved. This works as long as you redirect users to somewhere in the EE Control Panel.
Download SC Publish Redirect
EE Support | Downloads | Add-On Version | Release Date |
---|---|---|---|
Not Specified | Download | 1.0.1 |
SC Publish Redirect Links
This entry was created February 4, 2010, 6:56 am.
This entry was last updated November 3, 2010, 6:12 pm.
Disclaimer: Information about ExpressionEngine add-ons is provided as a service to you, the user, and every member of the ExpressionEngine community. devot:ee is not responsible if you hose, mangle, wreck, or otherwise destroy your EE website by installing an add-on that you found out about at this site, regardless of its rating, Favorites status, commercial or free status, or general popularity. Caveat EEmptor!
Returns: devot:ee has a 30-day return policy on all commercial add-ons sold through devot-ee.com. If you need to return an add-on, do not go to the developer or the developer's site, but rather visit our returns page at https://devot-ee.com/returns to initiate your return. If you have questions, email support@devot-ee.com.
2 Reviews:
J3roen 12.29.10
@kgrote: you need to change the extension priority for SC Publish Redirect to have it work with structure.
They both use the same hook and structure has a lower prio hence it is called last. Change it to 20 (for example) and you’ll see it’s working.
Sneed's Feed & Seed 12.22.10
Installed this add-on on a site running EE 2.1.2 and the Structure module and it didn’t work. I was still redirected to the dastardly publish summary page.