I’m thinking of a Batch edit form (20 last posts for example). You make all the changes to those entries and with one submit button they will all be updated.
To do this I removed the <input type=“hidden” name=“entry_id” value=”{entry_id}” /> and return=“weblog/edit_entry/{entry_id}.
I think I got closed to it but couldn’t finish the job. Is this possible with the plug-in?
There is nothing in EE that will support the simultaneous updating of multiple entries like you want. You would have to write custom code to handle that.
Solspace, this is a really really awesome plugin, thanks for writing it!
I needed to pull content directly from the database, like Chris said above, so I added some code to the plugin. I’ll paste it here if anyone wants to use it:
// ---------------------------------------- // Field Contents // ---------------------------------------- // This function returns the unformatted // field contents pulled directly // from the database // ----------------------------------------
I have to apoligise to Solspace for being stupid about the so-called “creeping” <p> Br/> and space “problem” because there is no problem.
The solution is right there in the Form Helper plug-in in the form of the {exp:form_helper:field_parser} {/exp:form_helper:field_parser} tag pair. The documentation is only slightly misleading because it implies that this tag is for custom entry fields, but it works for the default fields ({body} etc.) also - so HOORAY and a renewed love affair with this plug-in for me!
Caution - I cannot be sure that this is all there is to it - all I know is that I was not using these tags before, and now that I do, the problem is gone. I am not sure what effect the code posted by spacey310 has on this, but I installed it anyway and edits are working brillianly without recourse to the control panel.
> The documentation is only slightly misleading because it implies that this tag is for custom entry fields, but it works for the default fields ({body} etc.) also
Actually, all entry fields are “custom” fields. The ones that come with an EE install are only put in a Field Group labeled “default” because they’re set up by default for you. You can edit and delete the summary, body, etc. fields just like all others; there’s nothing inherently different between them and any fields you set up.
Chris - thanks for clarifying. I mistakenly thought that the defaults were somehow not custom.
Further to my previous post, there is still an issue, because while the <p> and <br/> tags have been eliminated, extra blank lines are still being entered, but I have not had time to see how these can be overcome.
Thanks for so much participation in this plugin. It’s really exciting.
The field parser bug has been bugging me too. So it’s fixed-ish. Download form_helper 1.3 from solspace.com/software and you will see that when on auto-pilot, the field_parser function parses much more smartly now. Basically I told it to remove exactly what EE puts into a field and replace with something smarter. Let’s see if it helps. Field parser still works as before if you want to provide your own parse strings.
And one more thing, it won’t work properly unless you make a donation and turn three circles while chanting Sue Sue Sue.
In SAEF there is a parameter for turning off the live url title (use_live_url=“no”)
Users like me who had this parameter set to no would have problem with their edit form because there is not a similar parameter and the form attempts to dynamically populated the url title.
There is also another reason way it is necessary to fix this, the linking mater. You see url titles should not be changed by changing the title by default. (It could be there as an option but not the default). There maybe people already linking to your post which you are editing.
