Forums / Developer / problem with creating classes (report as a bug?)

problem with creating classes (report as a bug?)

Next topic

Author	Message
Marko Žmak	Monday 22 August 2005 11:27:20 pm This is what I did: - made a copy of one of my custom classes - edited that copy and changed it's display name and identifier to "menu_item". There was already a class with that identifier, so eZ complained about it. - then I deleted the exsisting class with "menu_item" identifier and tried again to change the identifier of the copied class to it. And then the problems started. I couldn't change the name and identifier of the copied class. Then I found out that I couldn't make any new classes. Creating new class works OK until I get to save it. I get an error message: Object ID not valid Object not available Also when I edit an exsisting class and try to save it, nothing happens, the class remains unchanged. I've tried to clear the cache, nothing happens. Before this incident I was able to create and modify all my classes freely. So did anyone have problems with this? Should I report this as a bug? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Frederik Holljen	Monday 22 August 2005 11:48:20 pm Definitely a bug. Please report. It might be worth it to check if you can reproduce it from a clean installation. If you can't it may be very hard to fix it.
Marko Žmak	Wednesday 24 August 2005 1:11:01 am Hm... Today I just logged in the admin interface, and the problem was misteriously gone. I can change the classes freely again. There were no changes to the sistem in the meantime. Do I still report this as a BUG? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Bertrand Dunogier	Sunday 28 August 2005 11:07:40 am Sometimes weird behaviour appears during dev and goes away the next day... most prolly related to sessions. Did you try to clear all cache when the problem was there ?
Marko Žmak	Sunday 28 August 2005 11:38:48 am Yep I tried clearing the cache several times, from the admin interface, using clearcache.sh, and also manually deleting the cache folder. But nothing happened. Only after a day (during which I did nothing) the problem disappeared. ??? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Bertrand Dunogier	Monday 29 August 2005 10:34:20 am The same stuff happened to me due to _ I think _ session stuff... next time it happens (I'm not wishing any bad stuff to you ^^), try killing the session from Setup/Sessions... it's as far as I know the only place after cache where stuff is stored.