I have started developing in 4.7 but now switched to 5rc1. In 4.7 I used nodeaccess module to achieve this simple security measure:
All stories accesible/viewable/searchable by both auth and nonauth except those created by user X
All pages accesible/viewable/searchable by both auth and nonauth except those created by user X
The rest of the content acessible only by authenticated users.
I have created a test site at test.mainsite.com and everything works on the test site as on the live site (mainsite.com) except the event module where the calendar links to the live site as opposed to the test site.
I have looked at the database and cannot see how the entries point to the url. Any clues as to what I need to do to get the test calendar pointing to the test site?
I use drupal 4.7.0 on the live site and 4.7.4 on the test site. I have cpanel access to the files and phpMyAdmin to edit the database.
I was able to upgrade nicely and visisted teh admin link provided.
My problem started when i choose to log out.
I am unable to login againas admin. It does not show any error. Just pages refresh like that and I see no admin link.
Intrrestingly, I tried to login from office and it went fine. I even changed default theme and its good.
It appears my home IP is banned in my own admin panel.
I still have FTP and DB aceess. Can anybody advise me how I can recover from this ?
I have a Drupal 5 beta 2 installation. It's installed.
I have a 4.7.4 installation as well.
I wanted to use the database of my 4.7.4 with my 5 beta 2 installation.
I created a new database and imported my 4.7.4 database in it, so basically I created a replicate of my 4.7.4 database, then I went into my Drupal 5 beta 2 settings.php file and changed the 3 things I have to change for database : user, password, database name.
I have often seen it repeated on Drupal forums that one should disable contributed modules prior to upgrading a site. The handbook page for "Upgrading from Drupal 4.5 to 4.6.3" states that disabling contributed modules is the first thing to be done in the upgrade procedure. http://drupal.org/node/30699
Is it still the case that disabling contrib modules before upgrade is necessary, and if so, why?