6.0.0-beta1
9/24/25

[#3002] Unable to save pages after cvs update error: "Save Failed: DB Error: no such field'
Summary Unable to save pages after cvs update error: "Save Failed: DB Error: no such field'
Queue Wicked
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester twells (at) smarterliving (dot) com
Created 11/18/2005 (7250 days ago)
Due
Updated 11/21/2005 (7247 days ago)
Assigned
Resolved 11/19/2005 (7249 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
11/21/2005 03:12:26 PM Chuck Hagenbuch Comment #4 Reply to this comment
Remember to pass cvs update the -d argument to create new directories.
11/21/2005 01:52:47 PM twells (at) smarterliving (dot) com Comment #3 Reply to this comment
Where do I find these scripts? A cvs update doesn't seem to grab them.
11/19/2005 01:30:19 AM Chuck Hagenbuch Comment #2
State ⇒ Not A Bug
Priority ⇒ 1. Low
Reply to this comment
Did the underlying db structure change between February and now?
Yes. There are two dated scripts in wicked/scripts/upgrades/ that make 
the necessary changes:

2005-03-03_page_id.php

2005-06-10_permissions.php
11/18/2005 10:42:56 PM twells (at) smarterliving (dot) com Comment #1
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Unable to save pages after cvs update error: "Save Failed: DB Error: no such field'
Queue ⇒ Wicked
Reply to this comment
After performing a cvs update to the current head today I am no longer 
able to save pages. I'm uncertain how old the previous install was, 
but I please it was a cvs snapshot from February 7th 2005.



When saving, two things happen. First an error is displayed "Save 
Failed: DB Error: no such field'" and the changes are lost, and second 
a PHP warning is logged in the error logs: "PHP Warning:  in_array(): 
Wrong datatype for second argument in 
/home/devtools/virtual_html/horde/wicked/lib/Driver.php on line 248"



Apache 1.3.34, PHP 4.4.1 + Zend Platform 2.1.1, Redhat 9



Please let me know if there's any additional information I can provide 
to help track this down. Did the underlying db structure change 
between February and now?



Thanks,



Tabor

Saved Queries