Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
OK, I know I was warned. And I know it's not supported to downgrade to a lesser version. And I know CVS is not meant for production.
But "I have a friend" who has worked on a CVS installation, and "he" was so happy with it that "he" wants to turn it into a production installation (downgrade to 4.6.3). Has any one had any success in doing this ?
I've tried searching for this to no avail. Apologies if it's been fixed elsewhere.
I upgraded fairly smoothly to 4.5.3-4.6.3, however I now get this error if I try to search or run cron.php
this for cron:
user error: Unknown column 'sid' in 'where clause'
query: DELETE FROM search_index WHERE sid = 257 AND type = 'node' in public_html/library/includes/database.mysql.inc on line 66.
I've upgraded to 4.6.3 and have updated the banner module. Banners in blocks work fine but banners at the top of the page called through the {banner} code in the xtemplate.xtmpl no longer work. Is there an undocumented change in how to call banners from the theme template? I am using the following:
After an update from 4.6.3 to actual cvs-version I (user nr. 1) have no access to (old) nodes. Frontpage shows nothing an I get access denied message on node view. If I create new content after update all goes normal.
Someone knows the problem?
I did a dumb thing and ftp'd my drupal site with Frontpage to create a backup. Now the site is total messed up.
I get the following error. The database is ok, it wasn't touched. Any Idea what I have to do to fix this problem.
warning: call_user_func_array(): First argumented is expected to be a valid callback, 'node_page' was given in /home/xxxx/public_html/xxxxx/includes/menu.inc on line 354.
I've got a csv file with about 130 users that need to be imported into drupal. I've been working with the user import module for a few hours now with no luck. Has anyone had any luck getting the module to work within postgres?
The errors stem from LAST_INSERT_ID() and passing a NULL to a not null field.