This forum is for questions about upgrading an existing Drupal site. Don't forget to read the UPGRADE.txt file that comes with every Drupal download.

relative path/base url issue in 4.7.0-beta5

I must say that the 4.6 to 4.7 series move has been the biggest, in terms of time spent anticipating when to upgrade and dealwith all the accompanying problems, that I have seen here since I have been a member. I have been fiddling with 4.7.0 from the beginning of it's first beta all the way to now. What a ride. I lost track of the changes and bugfixes. It's awesome software. However, one particular thing that is irking me now are relative paths. Earlier I knew where I stood. You plug in your base url into the settings page and boom...everything worked. Even with legacy data. Not so in 4.7, at least with egacy data.

As can be seen here: http://drupal.org/node/51382, here: http://drupal.org/node/13148#comment-77673, and here: http://drupal.org/node/51612 this is an ugly little problem.

Two immediate issues I have. First, all internal links created by users pointing to other internal pages are broken. Nasty.Second, when the source code of each page is viewed in a browser, you get Login instead of Login, which I natrally do not want. In other words, the folder where things live is being shown.

I have read all about this in the changelogs, particularly for themes. Can someone PLEASE tell me how to just get things working(just the links and paths).

Bèr Kessels has been kind enough to offer this patch "phptemplate_engine_add_base_url_0.patch" here http://drupal.org/node/51612. Only problem is, I do not know what is meant by putting the "base tag" on the "page.tpl.php" page. So I can't even test it. What exact tag and where exactly on this page? Any help would be appreciated. My prediction is people with reams of legacy links who upgrade to 4.7 will be very unpleasantly surprised, unless of course, an easy to implement solution is there. From all the posts I've read, and I've spent many, many hours(yes, I'm embarassed!) on this, there is not yet one available. Any

error in upgrading to 4.7.0 beta 5 after site cracking

sorry for my english!

hello, tonight my drupal site has benn hacked. i had 4.6.4 version and all addresses gave back blank pages.
i looked at the database and it seemed all right so i tried solving the problem upgrading to the 4.7.0 beta 5.
when i ran the /update.php i received lots of errors:

* user warning: Unknown table 'page' query: DROP TABLE page in /web/htdocs/www.botulinux.net/home/includes/database.mysql.inc on line 120.
* user warning: Duplicate column name 'module' query: ALTER TABLE vocabulary ADD module varchar(255) NOT NULL default '' in /web/htdocs/www.botulinux.net/home/includes/database.mysql.inc on line 120.
* user warning: Unknown column 'voters' in 'poll' query: ALTER TABLE poll CHANGE voters polled longtext in /web/htdocs/www.botulinux.net/home/includes/database.mysql.inc on line 120.
* user warning: Multiple primary key defined query: ALTER TABLE term_node ADD PRIMARY KEY (tid,nid) in /web/htdocs/www.botulinux.net/home/includes/database.mysql.inc on line 120.
* user warning: Duplicate column name 'tags' query: ALTER TABLE vocabulary ADD tags tinyint(3) unsigned default '0' NOT NULL in /web/htdocs/www.botulinux.net/home/includes/database.mysql.inc on line 120.
* user warning: Can't DROP 'title'. Check that column/key exists query: ALTER TABLE boxes DROP INDEX title in /web/htdocs/www.botulinux.net/home/includes/database.mysql.inc on line 120.

4.6-->4.7: unknown column 'theme' in blocks

So, I copied my db over to a test db, and made sure to uncheck all non-core modules as well as change the theme to bluemarine. Then i untarred the drupal 4.7 files into a clean directory and changed settings.php.

When i ran update.php it autoselected version 133 (i'm not sure if this is correct, though) and ran with no problems. No errors were displayed on the screen.

When i try to go to my site, though, i get the following message:

------------------ message starts here ------------------

Need some help concerning upgrading from 4.6 to 4.7..

Hi Everyone..
I've been doing a upgrade from 4.6.5 to 4.7 beta 5 today and I've ran into some problems..

These are the steps I've gone trough..

Background: The site earlier ran on Xtemplate theme and had some 4.6 module inside the modules directory..

1. I'm importing the MySQL dump into MySQL and everything seems to be running smooth
2. Downloading Drupal 4.7 Beta 5 and extracts it and starts uploading it to the directory where the site is located..
3. After that I'm checking in the settings.php and everything looks OK..
4. I'm running the update.php script and everythings looks perfectly and everything is nice, no problems so far and no problems immediatly after the upgrade, no problems reported.. As I didn't had an account to login when I started the upgrade I changed to $access_check = FALSE; and no complaints about this..5
5. When the upgrade was ready I restored the line to $access_check = TRUE; And then hit the link to Administer settings..
6. I got up Access denied and when I went to the main page it was just showing content, no sign of drupal whatsoever, no CSS..
7. I tried to change the 4.7 beta 5 default theme called Bluemarine to the name of Tarmac which was the name of the old Xtemplate theme.. No effect..
8. I tried to delete all the 4.6 modules and just upload 4.7 beta 5 modules.. No effect

So now I'm wondering what to do.. What's the problem?

Update ONLY Node tables to 4.7

Hey all,

Slashed!

I just upgraded to 4.7 B5 from B4 and a very odd problem popped up.

At first I thought some of my menu callbacks were faulty, but no. It was actually the way I was doing links. Something happened with a trailing slash somewhere and caused my links to stack up relative to the path.

For example...

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal