Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I should have added that I'm asking about the database specifically. The update.php script just sits there and spins when I tried it on my sandbox. I cancelled it and am now wondering if I need start over. I don't believe the patches or 4.6.4 include any db updates but I'm not sure either.
There are a couple of patches for update.php in the hopper already. There arn't any db updates, so go through the issue tracker and take a look at patches for update.php.
I'm having the same issue but haven't had time to look at it yet so hopefully tonight I'll be patching.
I tried upgrading 4.6.3 to 4.7 beta unsuccessfully.
I switched back to 4.6.3 but now the contents are not present if I'm an anonymous user. If I log in with my username, then all the contents magically pops up.
I checked permissions and are all ok...
What Did I broke, in the DB, to spawn this damn problem in my site?
a, it's a BETA release! Not even a full out almost ready for production release. Shockingly, the release announcement itself mentioned asking for your help in finding and PROPERLY reporting these problems.
b, From the release announcement there are links on where to look for reported bugs and the place to report these issues hasn't changed in several release versions. Some 'someone in the know' has already told you were to look for what is being done to fix these issues.
d, if you upgrade your production site to this code after repeated warnings about it being beta, then well.... what can we do? Mention you were warned?
I admit I was an Idiot, for not doing a regular backup of my DB.
But now, the mess is done. That's it.
I'm only asking for help from a Drupal techie now.. Simply, why my contents are not displayed if I'm anonymous, and when I Log in, the contents immediately pop up???
What is wrong in the db? In the past 3 hours I played around with the db... I'm getting crazy.
You penned a message of alarm that 'someone' should announce something as it was 'alarming' that there were problems. I responded to it by pointing out that 'someone' already had and pointed back to all the information links on how to help out.
As to what someone can do now if they don't have a backup.
Backup their database now.
Read the best practices link.
Look in the issue tracker for any issues with updates and permissions (anonymous user access).
Download the CVS version and run update again from a newer CVS install (AFTER YOU'VE BACKED UP YOUR SITE). At this point the data is still there (unless something has gone horibly wrong). It's just not accessable in the expected way.
At this point the CVS version is a repackaged version of Drupal HEAD. At some point this will change. It is packaged from all commits about every 12 hours.
Other ideas.... Install a test site with 4.7. Add rough content and configure the permissions like your production site. Start comparing various table entries. If in the clean install, anonymous access works, then you start looking at places where this is set and change them directly. Track what you change so you can set it back.
Comments
I should have added...
I should have added that I'm asking about the database specifically. The update.php script just sits there and spins when I tried it on my sandbox. I cancelled it and am now wondering if I need start over. I don't believe the patches or 4.6.4 include any db updates but I'm not sure either.
issue tracker, issue
issue tracker, issue tracker.
There are a couple of patches for update.php in the hopper already. There arn't any db updates, so go through the issue tracker and take a look at patches for update.php.
I'm having the same issue but haven't had time to look at it yet so hopefully tonight I'll be patching.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
Tanx
ooog. Egg on my face again... off to search and read.
You can also follow cvs
You can also follow cvs commits.
http://drupal.org/project/cvs/3060
or have them emailed to you by project.
http://drupal.org/project/issues/subscribe
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
Content disappearing when Anonymous
I tried upgrading 4.6.3 to 4.7 beta unsuccessfully.
I switched back to 4.6.3 but now the contents are not present if I'm an anonymous user. If I log in with my username, then all the contents magically pops up.
I checked permissions and are all ok...
What Did I broke, in the DB, to spawn this damn problem in my site?
Please help :D
Greetings from Italy
alarm bells ring in my ears
from what I have noted on these forums I would definitely say that there are more than a few problems with making the move to 4.7 beta1.
I would like to ask those in the know to make some public announcement as to what the solution to upgrade problems is.
It seems to me that many people will be wasting a lot of valuable time on this if nothing is put in place to correct the problems.
wellsy
orchidsonline.com.au
oh stop it
a, it's a BETA release! Not even a full out almost ready for production release. Shockingly, the release announcement itself mentioned asking for your help in finding and PROPERLY reporting these problems.
b, From the release announcement there are links on where to look for reported bugs and the place to report these issues hasn't changed in several release versions. Some 'someone in the know' has already told you were to look for what is being done to fix these issues.
c, chx is even offering a bughunt compitition.
d, if you upgrade your production site to this code after repeated warnings about it being beta, then well.... what can we do? Mention you were warned?
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
but i guess people want to help is all
So we cautiously start
a) go about the upgrade path on our test sites
b) nothing useful happens
c) we get shouted at for pointing this out.
d) no useful help is forthcoming to help make anything work in our test sites after the upgrade destroys them
So where do we all go to find a way around the upgrade mess at the moment which is fairly obviously not working for many people at this time?
We are all here trying to give some help to the community but simply need your help to allow us to do this for you!
wellsy
orchidsonline.com.au
I admit I was an Idiot, for
I admit I was an Idiot, for not doing a regular backup of my DB.
But now, the mess is done. That's it.
I'm only asking for help from a Drupal techie now.. Simply, why my contents are not displayed if I'm anonymous, and when I Log in, the contents immediately pop up???
What is wrong in the db? In the past 3 hours I played around with the db... I'm getting crazy.
alarmist posts get a response
You penned a message of alarm that 'someone' should announce something as it was 'alarming' that there were problems. I responded to it by pointing out that 'someone' already had and pointed back to all the information links on how to help out.
As to what someone can do now if they don't have a backup.
Backup their database now.
Read the best practices link.
Look in the issue tracker for any issues with updates and permissions (anonymous user access).
Download the CVS version and run update again from a newer CVS install (AFTER YOU'VE BACKED UP YOUR SITE). At this point the data is still there (unless something has gone horibly wrong). It's just not accessable in the expected way.
At this point the CVS version is a repackaged version of Drupal HEAD. At some point this will change. It is packaged from all commits about every 12 hours.
Other ideas.... Install a test site with 4.7. Add rough content and configure the permissions like your production site. Start comparing various table entries. If in the clean install, anonymous access works, then you start looking at places where this is set and change them directly. Track what you change so you can set it back.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide