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 so I am upgrading from D6=>D7 and get this error message:
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://example.com/update.php?op=selection&token=2vzyQWm3OPvPW2zqi1KMKOgK1ZPbBN5OhB6XIFgjUYg&id=6&op=do StatusText: OK ResponseText: Fatal error: Call to undefined function _update_7000_field_read_fields() in /home/example/public_html/modules/field/modules/text/text.install on line 78
I chose Drupal 6 because the structure of the database for custom content types was closest to our data model, albeit with the centralised Node table added. It works better in terms of normalisation and in terms of our system this was vitally important to us. We have been building logical data models for 30 years and the idea of doing everything from the front end and using the hideously convoluted views method to pull out data in awful SQL queries makes little sense to us.
Anyway, point being that the data model is still extremely important to us, but we are aware that the need to upgrade to Drupal 7 is going to get ever more urgent. My question is whether it is possible to keep a similar data structure, or whether you have to use the method that Drupal has adopted for its database in its core CCK module. The idea of having a table for each field, as I understand is the case, is so completely absurd to me that it makes me a bit nauseous. If I'm wrong, please correct me because I would love to be wrong about this.
trying to upgrade drupal 6 to 7. but when open site.com/update.php, error message as below http://i.imgur.com/T3sGJ.jpg
below is the step that i use:
1) off-line
2) choose garland theme
3) disable non-core modules
4) remove default.settings.php
5) delete all folder and files excepts sites folder
6) copy all drupal 7 files to directory
7) setting.php permission set 666
I am trying to upgrade a working 6.26 installation to 7.x. I followed the update instructions to the letter and got everything uploaded and edited. When I tried to run the upgrade.php script, it immediately forwarded me to install.php and displayed this:
Now I know that the Drupal community has a strong attitude against allowing automatic updates as a core feature, but excluding it is a deal breaker for me. I have spent hundreds of hours with drupal with joy until reality kicked in and I realized that it is just not practical for me to use for any site of significant value. It came to a point where the cms would break almost every 15 days, and required at least 6 - 12 hours of extra work to safely transition from the rapidly outdated versions of drupal. In the past I had almost been an evangelist preaching the underestimated value of the drupal cms. If it's true that Drupal is used by millions of people then it's likely that millions of man-hours are being wasted in frustration on this with many thousands of sites going extinct because it is too much work to maintain.
WordPress is a practical solution as it offers automatic updates. Could you imagine what would happen if Microsoft Window's was incapable of having automatic security patch updates and upgrades? Microsoft can do it, WordPress can do it, Drupal 8 and Dupal 9 ought to be able to do it. It's not a matter of it being too difficult, it's just a matter of being stuck in old habits and being unwilling to change.
Whener I try to run the update script I get the message Libraries (Version >=2.x required).
However, the Libraries is already the version 2.0
I can't install anymore modules, nor upgrade my website!!!