Ok, here’s two more additional requests for functionality (adding to my post above in this thread) I would also like to see in a pie in the sky world:
1) Combine Mark Huot’s “Duplicate” extension (adds “Duplicate” button in same publish page area) with PPI Ext so that it is another bulleted option with the others, and
2) Be able to apply these individual setttings on a per weblog basis.
So, version 1.2 has arrived. This has a bug fix and addresses another two of my pet peeves:
I haven’t ignored your other feedback. I’ll address some of it here, and work on the rest of it as I can. Arden, * I don’t think it’s wrong to call quick save baffling; I have never had a client be NOT baffled by it. * If you’d rather keep the Quick Save button, just change the language file to call the “Save” button “Quick Save” and then hide the real “Quick Save” button. Yes, that means you’re still doing a full submit, but that’s not the end of the world in most cases. * Ditto for changing the language of the control panel page text.
I’m probably not going to add features that are opposites: I won’t add something that hides the real save button, for example, because then I have to add logic that deals with what happens when you hide both buttons and now you can’t save at all. Well, I guess I could let people make their own messes… Hmmm. It would take a rewrite of the way I look for what to change… Hmmm.
As for applying it on a per-weblog basis, again, that makes it really complicated in the settings department, and I probably won’t go there.
Hiding the upload link entirely, that seems doable. Watch this space….
TTFN Travis
I don’t think it’s wrong to call quick save baffling; I have never had a client be NOT baffled by it.
Either way, it’s a matter of opinion as to whether or not it is “baffling,” and does not belong in the description of the Quick Save button. Control panel preferences are not the place to give your opinion on the usefulness or confusingness of a feature because it’s really not your call once you’ve released the extension.
I, for one, find the Quick Save button quite useful because I can save my progress and not have to navigate back a page to continue editing, much like the Save function of most document-based applications. It seems that your clients aren’t the brightest bunch if they can’t figure that out, but that’s just my opinion — which is the whole point, it’s your opinion vs. my opinion on how useful it is, so you shouldn’t pass judgment in the first place. At least not in the extension itself. You can argue on here all you want and that’s your right, but subjective language does not belong in an objective context.
Anyway, this is all kind of off-topic. I’ll be downloading and playing with the extension as soon as I post this, so thank you in advance. 😊
Very cool! Thanks! If you have an opportunity it would be great to have the option to disable the preview button too - just a reminder. Thanks, I’m going to check this out now. 😊
update: just checked it out and pretty cool. Noticed that the direct edit button is not showing up on the CP homepage for me?
I really like the save as new feature. Thank you for adding that!
Updated. You can now customize and/or remove any of the buttons on the publish form. But don’t remove them all. That’s just silly.
Go back to the first message to download the current version.
Uggh - moved the extension onto another build I have for testing (already had the previous extension version added) and received this when trying to log into the control panel:
Warning: call_user_func_array() [function.call-user-func-array]: First argumented is expected to be a valid callback, ‘publishimprove::add_copy_checkbox’ was given in /usr/local/www/site/system/core/core.extensions.php on line 189 I can’t seem to log into my control panel…
========= I deleted the extension / language files - hoping I could then login in but now I get:
Error
Unable to load the following extension file:
ext.publishimprove.php
=====
Added back the previous version of the extension but received this:
Warning: call_user_func_array() [function.call-user-func-array]: First argumented is expected to be a valid callback, ‘publishimprove::change_template_tab_behavior’ was given in /usr/local/www/site/system/core/core.extensions.php on line 189
Rob Q: It’s very important to disable the extension before updating it. This is good advice for any extension, but required in this case.
I think (but I’m not positive, so BE CAREFUL) that you can fix this by editing your database directly, going to the exp_extensions table, and removing the hooks for this ‘publishimprove’ extension.
TTFN Travis
The exp_extensions table contains a list of the extensions you have installed, and the hooks that they will triggered on, and the name of the functions that will happen at that triggering time.
If you delete every row in that table that contains “publishimprove”, that should take care of your problem.
Another temporary solution would be to disable ALL extensions via the setting in your config file – it’s the “allow_extensions” setting – but you wouldn’t be able to re-enable them until you fixed the underlying problem.
TTFN Travis
A couple of problems I seem to be having with this extension:
I’m able to add a text link to the Upload icon/graphic but I’m unable to remove the Preview & Quick Save buttons or change the Submit button text. As far as I know, I’ve installed/enabled the extension properly and I’ve changed the Extension Settings to what I require.
Thanks for any help!
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.