No, I just read through it, isn’t that just so you can have the ability to remove the upload file functionality?

I was saying that this extension afaik is conflicting with the Playa extension when you have more than 1 playa field in your field group. Would the above mod fix this?

they inspire - 25 February 2009 09:02 PM

No, I just read through it, isn’t that just so you can have the ability to remove the upload file functionality?

I was saying that this extension afaik is conflicting with the Playa extension when you have more than 1 playa field in your field group. Would the above mod fix this?

Check post #33. I had a similar problem with sequential related gallery dropdowns, the mod in #33 fixed it for me. the post after that is if you want to add the option to remove upload file via a setting.

hey man, thanks a lot. That fixed it actually. Much appreciated! cheers

np glad it’s basically the same problem we’re all having or rather the ‘solution’ is a one size fits all sorta thing.

Wiki’ed.

I’ve found a pretty serious bug with 0.7.2 (not sure about other versions).  By default, the system will truncate textareas in the CP so you can’t get more text in there than MySQL will allow.  With this extension enabled, it appears this doesn’t happen - it will allow you to enter more characters than MySQL will allow.  If you go back and try to edit your entry again all you get in the CP is a blank white page - no PHP errors, no nothing.  The front end of the website will show the content so it isn’t quite as bad, but you can’t get back in to edit at all (you have to go into MySQL and modify the field manually).

I’ve just turned off the extension for now and everything is back to normal, but would love to know when it’s fixed.

Thanks!

Aenarion - 11 February 2009 03:07 PM

I get this error when I get to the Edit page:

Notice: A session had already been started - ignoring session_start() in /home/xxxxxx/public_html/xxxxx/extensions/ext.publish_tweeks.php on line 151

FYI—I fixed this by doing the following to both session_start() lines:

New Release 0.8!

http://www.ngenworks.com/software/ee/publish-tweeks/

CHANGELOG

• Redesigned the message area when an entry is updated to be more noticeable
• Bug fix: suppress session_start notice message
• Bug fix: moved button text to language file
• Bug fix: moved update/saved message to language file

Fred/Travis,

Nice to see nGen File Field worling like a charm now. Last I tried it, there were some issues with Playa, but doesn’t seem to be a problem now - Not sure if you guys or Brandon fixed that, but good to see it good and dandy now.

I think using this makes a lot of sense with nGen File Field since the default redirect behaviour to the preview page is pretty pointless (as it doesn’t show image previews). Add in an LG Live Look tab and you’re pretty good to go with a publishing workflow that is more sensible.

I think a delete button appear beside the save button after a submission has been saved makes sense. It’s tedious enough having to go into edit, select a check box, choose delete from a dropbox, then clicking submit. Just a suggestion!

Thanks for this addon, it looks extremely handy. One thing that occurred to me is that I don’t really want the ‘Saved!’ message hanging around once the user has updated their entry. If they keep working on it and then save again there is no new element on the page to confirm that they update’s been successful, as the ‘Saved!’ message was already there from the last update.

Fortunately a little bit of jQuery makes it really simple to have the saved message fade out after a few seconds:

I imagine there are lots of ways you could add this to the markup. I’m using Leevi’s Add Sitename extension, so I just placed it in the XHTML field that includes. The above code will make the saved message disappear after 5 seconds - you can adjust that by modifying the 5000 variable.

@Dom.S - Genius!  Excellent tip.

It would be really great if Dom.S’s code were added to extension!

Hi again,

Found a way to add Dom.S’s code to extension.

To add it open the file exp.publish_tweaks.php in text editor and found the line 175:

Change it with this code:

THat’s it! Now the message “Saved!” will fade out after a few seconds.

Hi Travis,

Just found that Publish Tweaks extension it does not play well with Reeveal Comments extension.

If Publish Tweaks extension is disabled, then Reeveal Comments works correctly, but with Publish Tweaks enabled Reeveal Comments does not work - no comments in Comment tab are shown.

It seems that Publish Tweaks somehow clashes with Reveal Comments extension and prevents it from working correctly.

Hmm that’s odd - I’ve got both those extensions enabled on my blog with no difficulties.

Using 0.8 I found an odd behaviour which looks like a bug. I am setting up a new website, and only have 1 weblog currently.  Using the publish tab, if I use the hover state and click on my weblog start a new entry then publish tweaks works fine. But, if I click on the publish tab to start a new entry (not the hover state name of my weblog), it automatically starts one from my one and only weblog, in which case publish tweaks doesn’t work - all buttons and the file upload link are all there.

I’ve noticed that the breadcrumbs in the CP to the publish page are actually different when getting there these two different ways - when it is working (click on the hover state of publish tab) you’re here:

CP Home ›  Publish ›  New Entry ›  Page

But if you just click on the publish tab and it starts one automatically for you you’re here:

CP Home ›  New Entry ›  Page

That’s not handled by your extension obviously, but thought it might help in debugging…

Thanks for the great extension!

Brian M. - 25 June 2009 12:33 PM

Using 0.8 I found an odd behaviour which looks like a bug. I am setting up a new website, and only have 1 weblog currently.  Using the publish tab, if I use the hover state and click on my weblog start a new entry then publish tweaks works fine. But, if I click on the publish tab to start a new entry (not the hover state name of my weblog), it automatically starts one from my one and only weblog, in which case publish tweaks doesn’t work - all buttons and the file upload link are all there.

Just want to confirm that I can replicate this behavior. Like Brian, I only notice it when there is only 1 weblog and I click directly on the Publish tab. Any ideas what might cause this?

Thanks for the awesome extension.

Jake

I love this extension. But it doesn’t play nicely with the equally awesome NSM Publish Plus extension, as it hides the required “Draft” buttons etc. If only this extension was more configurable: rather than simply giving the option to remove the upload file box, it’d be great if we could choose what options we wanted to action. So, for me, I’d want to have it redirect to the same page; I’d want it to remove the file upload box; but I’d want it to leave the draft buttons etc.

Is this possible? Or am I missing something?