I tried upgrading on my live site and it didn't convert to 6.16, so I restored everything and it is running on 6.15.
I duplicated the site on my local host and it ran perfectly with no warnings other than the 6.16 upgrade warning. After trying to upgrade to 6.16 I get the following warning.
warning: Parameter 1 to profile_load_profile() expected to be a reference, value given in C:\Program Files\xampp\htdocs\public_html\includes\module.inc on line 462.
I'm habing a problem when I upgrade a couple of modules on my site. Hopefully somebody out there ran accross this before.....
After running the "Available Updates" on my site, I was notified that the two following modules are out-of-date:
Revisioning 6.x-2.7 (needs upgrading to 6.x-3.6)
Module Grants 6.x-2.6 (needs upgrading to 6.x-3.5)
I downloaded each of these modules, backed up my database and file structure, and replaced the two module folders in my site. When I refreshed my page, I received the following message:
Is there anything can help me to upgrading drupal ,my version is 6.12 and I want to upgrade in version 6.16 in subversion system,is there anything can help me???
HI guys, another "please help out" thread from me.
This time it´s about the file system. I´ve recently moved my site to the web, but of course the file system coulden´t handle this.
So I wonder, what folder I should type in for the "File system path:" and what folder for the "Temporary directory:"
Yeah, I understand that you can´t tell me the name of the folder, but where should I put this folder?
Hello
I upgrade 6.15 to 6.16 and I have error
Parse error: syntax error, unexpected '<' in /usr/home/domain/public_html/modules/statistics/statistics.module on line 322
This error is only for authenticated user or administrators.
I have attempted to update from 6.15 to 6.16, multiple times now. I get the semaphore table error every time.
Other forum posts claim trying update.php repeatedly creates the semaphore table, and completes the update. Beyond the error (and the fact that my install is still clearly at 6.15), this all wasn't terribly problematic.