Closed (won't fix)
Project:
Custom Formatters
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 May 2011 at 20:45 UTC
Updated:
3 Aug 2011 at 11:30 UTC
Jump to comment: Most recent
Comments
Comment #1
merlinofchaos commentedThis one will require knowing more about what's going on at that exact moment to debug.
Does this happen *only* on the profile2 admin page? If so, maybe it's a profile2 issue. Though I don't see a dependency on ctools for profile2, so I don't know if there's really a link there or not.
Comment #2
sosiris commentedComment #3
e2thex commentedI just had a similar issue with field_groups. And it turns out that I was missing a few db_updates on the field group module. They had add a field, and ctools was trying to find it. After I had those upgrades run, the issue went away.
(I am not sure how it happened but my system table had them run even though they had not been run yet)
Comment #4
ghmercado commentedi get these all the time on my d7 header:
Notice: Undefined property: stdClass::$mode in _ctools_export_unpack_object() (line 775 of /home/myusersite/public_html/sites/all/modules/ctools/includes/export.inc)
particularly after a cron or clear cache.
site works alright however. After a page refresh the error goes away.
i have tried reinstalling to same results. i also have fieldgroups btw, could that be culprit?
tia
Comment #5
pglatz commentedDitto; I see them after clearing all caches, but they disappear after that.
Comment #6
ghmercado commenteda new observation: I 100% consistently get those errors when i load:
/admin/structure/types/manage/blog/fields
or any content type. hope this helps track down the problem.
Comment #7
omercioglu commentedThis is caused by custom_formatters module. I've installed this module in its early stages.
Now that i look at it's database schema(formatters table) i can see that the "mode" field is not there.
Also there are some left over examples which are not visible on the admin page. I've deleted these old entries, added a mode field to the table, fixed my old formatters accordingly and now the error is gone. You can also try uninstall/reinstall the module, but i don't think it will delete/fix these old data.
I guess an update function in needed to fix this schema/old data issue...
Comment #8
decipheredomercioglu,
There is and will be no upgrade path from Custom Formatters 7.x-1.x -> 7.x-2.x as there was never an official 7.x-1.x release. If you uninstall and re-install the module you will have the correct schema.
Comment #9
omercioglu commentedI see.
Comment #10
Anonymous (not verified) commentedAs Deciphered recommends, backup your code, disable 1.x, uninstall, install 2.x.
Comment #11
bryancasler commentedsubscribe
Comment #12
bryancasler commentedJust installed the 1.x version and then uninstalled it. Then I installed the 2.x version and uninstalled it. Let's see if that squares everything away.
Comment #13
bryancasler commentedIt did not work
Comment #14
bryancasler commentedEnabling the 2.x version and seeing if that will somehow prevent the errors from occurring.
Comment #15
bryancasler commentedThat does not work either.
Comment #16
bryancasler commentedActive discussion on the issue happening over here #1209576: problems with ctools on update.php and login pages