I am afraid I have too many various hook_form_alter calls going on in my forms (from File Framework attachment, and Notification).

Basically I get the 'Next' button on the initial form, can move to the following screen to select terms, but my selections are not saved when I press the 'Save' button just below the terms or otherwise if I save at the bottom of the form. In both cases, when I press save, it's as though nothing has happened. I get no warnings or errors.

If anyone has any insights, I would appreciate them. Like I said, I wouldn't be surprised if this is an idiosyncratic issue of having too many form alters, but some perspective would be great.

Comments

Equinger’s picture

Equinger commented
Category: support » feature

Ended up figuring this one out myself. I recently enabled page caching.

The issue had to do with "Normal" Page Caching in '/admin/settings/performance'. The module is incompatible and works bizarrely when this is enabled (won't save, pressing save makes the Form choke sometimes').

Would love to be able to enable page cacheing, but I'm really glad I figured this one out cause like I said, I want to use it first and foremost.

Equinger’s picture

Equinger commented

This is still a legit issue. Any ideas?

Eric

sdrycroft’s picture

sdrycroft commented

Thanks for this Equinger, I've been having exactly the same problems on my sites, and have been investigating. I'm working on a fix, although I'm also working on a version two of the module, which will work slightly differently.

Equinger’s picture

Equinger commented

Thanks for your attention to this, sdrycroft. I am looking forward to the new version of your module. This is an important module for really moving forward w/ systematic tagging of content w/ custom vocabs and faceted search and whatnot. Thanks for your work!

Eric

sdrycroft’s picture

sdrycroft commented

Version two of the module has now been released. Please try this, and let me know what you think.

sdrycroft’s picture

sdrycroft commented
Version: 6.x-1.25 » 6.x-2.0
Issue summary: View changes
Status: Active » Fixed

It looks like 6.x-2.x fixed this.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.