For some reason beyond my understanding after installing the mod on the latest version of Drupal without any errors I cannot save the settings at admin/settings/calais/calais-node
I hit save and then it goes back to the calais settings but nothing is saved.
Also batch processing gives me the following: An error occurred. /batch?id=13&op=do <br /> <b>Fatal error</b>: Call to undefined function dpm() in <b>/sites/all/modules/opencalais/calais.admin.inc</b> on line <b>416</b><br />
Comments
Comment #1
febbraro commentedLets try fixing that batch error first and maybe that will fix the other problem you are having (doubt it, but it's a start)
Try this patch to fix that dpm() problem you are having. #429560: Flaming red errors upon bulk processing Either that patch or install/enable the devel module until I get the next release out, or use the dev release.
Comment #2
Zarevac commentedYep, batch got fixed with the dev release.
However still no change in saving, Ill install Devel and get back to you.
Comment #3
Zarevac commentedI activated Devel and checked some things out, but don't see anything strange. What should I be looking for exactly? I uninstalled the mod and re-activated it again but no avail.
Comment #4
febbraro commentedStrange indeed, but this is not the first time I have heard of this. Not sure if other modules have had similar issues.
Can you try to debug a bit? In modules/opencalais/opencalais.admin.inc there is a function calais_admin_settings_submit that handles the save from clicking the submit. Can you put some prints/debugs in there to see if it even gets there? Could be a FAPI problem if that function us never getting called.
Try something simple like changing:
to
The dpm function requires the devel module, use print or drupal_set_message if you dont have devel enabled anymore.
See what that turns up. Thanks.
Comment #5
Zarevac commentedOK made the changes and Devel is still on, dont see anything strange. No errors afaik. But then again I dont know what to look for and I am not that experienced with Devel.
I was wonderin if Mod Secure could be an issue? Not that I can/will turn it off.
But e.g. menu re-ordering inside the admin never works with me due to mod_secure
Comment #6
febbraro commentedUpon a "save" when the page refreshes where you might normally see "Setting have been saved" you should see the mesages you put in to print. If you dont see them, that tells me it is never even getting to the submit handler.
Any clue what mod_secure was doing to screw up that menu reordering?
Comment #7
Zarevac commentedAfaik no "Setting have been saved" message.
Mod_secure blocks the ajax that Drupal uses to re-order the menu's in admin. So re-ordering is possible but only by accessing each menu item and editing them with the drop box.
Comment #8
Zarevac commentedI double checked the mod_secure logs but there is nothing in there for calais. I do not see however that the Settings are saved so there must be another cause.
Comment #9
febbraro commentedUnfortunately I can't reproduce it, so I can't help much in debugging.
This is the first function that gets called on submission, http://api.drupal.org/api/function/drupal_get_form/6 that is where the debugging will have to start to see what path it takes through that function. That is what is supposed to determine that the form was submitted and it is time to save and call any/all submit handlers and validation handlers.
If I can get this behavior to happen for me I will dive in. If you discover anything else, please let me know.
Comment #10
lennyaspen commentedsame problem here
waiting for a solution
Comment #11
febbraro commented@lennyaspen Sorry I can' reproduce it (using this on 10+ sites), but if you can any information you can provide to help me or others get to the bottom of this I'd greatly appreciate it.
Comment #12
lennyaspen commentedsorry i thought it was the same so i didn`t post it
i`m not to much of a developer so if you want anything else ask me...
btw very nice module
Comment #13
febbraro commented@lennyaspen see #429560: Flaming red errors upon bulk processing this is a different issue
Comment #14
Webster619 commentedsame problem here.
Comment #15
sprentic commentedSeeing the same error of not being able to save node settings (It accepts the api settings and key but not node settings). Drupal 6.14
I compared this with another instance ( 6.10 upgraded to 6.14 ) I have that is working and found that the variable table did not have all the settings ( especially node settings ).
Might try and export / import variables to see if that fixes it.
Comment #16
fcolas commentedi am running into a similar problem.
it occurs that after submitting the form, the update / insert statements proceed but in the end, the calais variables are deleted by some DELETE FROM variable blablabla.
i don't know why...
maybe a reset to default, or something to do with the cache that is cleared right before the delete statements...
rk: i inserted manually the variables and at the next call of the open calais settings page, the variables appeared properly set. so, the retrieval of the data is not the problem.
Comment #17
febbraro commentedComment #18
Anonymous (not verified) commentedSame problem here with latest dev release and "normal" release.
I'm not able to save the node settings
Comment #19
Anonymous (not verified) commentedIt was a Suhosin issue. Now I can save the settings.
Comment #20
oscarm22 commentedWhat was the issue?
Comment #21
nickgunman commentedWhat was the issue with Suhosin and how did you solve it?
Comment #22
BusinessMediaCenter commentedI am unable to save any settings as well. This was marked as fixed but no solution was ever given. Please advise and/or fix, otherwise module is unusable. Using latest 6.x dev release. Also, when running cron, status page indicates this error,"Calais integration module is enabled, but the settings have not been saved."
Thanks