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.
For weeks now I have been receiving a message that I must update my version of Drupal. Finally, I upgraded tonight using Simple Scripts provided by my IP provider, FatCow. When I tried to log in to my blog, I was greeted by a 500 error message. I have yet to be able to log in and my visitors can't either. What should I do?
Hi,
we are pretty new as Drupal users, and we just upgraded our systems from drupal 6.26 to drupal 6.28.
We followed all the instructions and the update seemed fine, but the spotlight doesn't show correctly the background image, as you can see here: http://www.esnbologna.org/
the problem is that it doesn't create the html correctly... it has a div tag of this type:
I just updated from ver 6.18 to 6.28 and all seemed to go well, however when I look at the "Status report" in Admin I see conflicting information. In one place on the page it says I am at version 6.28 yet further down that page it says "Drupal core update status Not secure! (version 6.28 available)." So what the heck is going on??
We have a Drupal 6 site, and we have been debating upgrading it to Drupal 7. We had a consultant look over our site and give us an estimate regarding how long it would take to upgrade our site. They estimated that 27 weeks would be required to upgrade our site from 6 to 7. Because this process has been estimated to take half of a year to complete, people that are not me have decided not to go through with the upgrade right now.
I do not think this is good because when 8.x is released then 6.x may stop being supported. I also wrote a module that I would like to contribute, but I think I need to release it for 7.x and eventually 8.x. If our site continues on 6.x, then this is not likely to happen. We also will be adding more custom modules which we may or may not contribute, and I am concerned that the modules will not be of much use to newer sites running on 7.x or 8.x.
My workaround for this is to keep our current site as is, but to do our new development on a 7.x site. The user would access the 7.x site through the 6.x site and make use of the 6.x's site's users, roles, groups, etc. In theory, this would allow us to develop our new modules on 7.x and contribute them to Drupal.org for others to use, but also it would eliminate our need to upgrade our current 6.x site.
HI
I have just set up a multi site drupal/civicrm environment using drupal 7.
I have a current environment on drupal 6 which has 5 live sites on it.
I would like to upgrade my drupal 6 sites to drupal 7 but also I woudl like to move them onto the new drupal 7 environment (which is on the same server).
I assume I woud be best ensuring that I update core and modules to latest versions on 6 before makign the upgrade and move to 7?
I am using Drupal 6.14 and Webform 6.x-2.9... If I update to Webform 6.x-3.X, my forms stop diplaying on the website... I want to update my core but not until I've updated the Webform module... I updated the core to 6.28 earlier and then tried to update the module and had the same problem, so I restored my database from a sql dump and a site backup...
How do I figure out why it's not displaying after I update the Webform module?