problem updating

upupax - April 29, 2008 - 12:16
Project:Views
Version:6.x-2.0-beta2
Component:Code
Category:support request
Priority:normal
Assigned:Unassigned
Status:closed
Description

I tried to update from my version to the newest one and everything went messed up.
I restore my backup, so everything is ok now, but I still would like to update: is there a way to prevent all the messing?
Thanks.

#1

lrickard - April 29, 2008 - 14:03

Could you provide some more information about the problem?

Especially:

  • what version of views are you updating to? (Beta 1? Beta 2? etc.)
  • what version of PHP are you running?
  • describe how "everything went messed up"

How to report bugs effectively

#2

upupax - April 29, 2008 - 14:59

I was updating from alpha5 to beta2.
Php is 5.2.0-8.
And "everything messed up" means that I got errors like missing contents and even an error about cache exceeding.
Maybe it's just my fault, but I'm a bit scared because the first time I updated from alpha4 to alpha5 all my views went lost, so I was wondering if it is normal (because of the alpha release) or if I'm doing something wrong.

#3

lrickard - April 29, 2008 - 15:58

Ah. Well, that's definitely nothing like the problems I was experiencing. Hopefully someone else can help you out. You can help by copying the text of the error messages and pasting them here, or attaching a screenshot of the errors. The more precise details you provide, the easier it is for the hard-working maintainers to respond. Try to give them the information they need to recreate the error for themselves.

How to report bugs effectively

#4

merlinofchaos - April 29, 2008 - 16:44

This is not a normal part of the update.

I will need the exact error messages to have any idea what's wrong.

#5

bixed - April 30, 2008 - 17:41
Version:6.x-2.0-alpha5» 6.x-2.0-beta2

I think i have the same problem on my local test setup using Views 2.0-beta2 on Drupal 6.2 on PHP version 5.2.5.

The exact problem is that when i try to look at a view or edit it (only those two actions) i get the error message:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 782352 bytes) in C:\wamp\www\drupal\sites\all\modules\devel\devel.module on line 1351

i have found out that this is only happening when the Theme developer module is enabled, not when only the Devel module is enabled.

I don't remember exaclty which version of i views 2 i was upgrading from, but it might have been alpha5.

#6

merlinofchaos - April 30, 2008 - 17:43

bixed: Theres another issue about Views + theme developer already; you should post on that one as the amount of memory you have available should be noted.

#7

bixed - April 30, 2008 - 19:19

I have posted a new reply in issue #241408: White screen on view/edit or add form when Theme Developer module is on with even more details

#8

merlinofchaos - May 2, 2008 - 18:58
Status:active» active (needs more info)

This issue is still waiting on the initial poster to provide more information.

#9

upupax - May 23, 2008 - 13:59

Sorry for the long silence, but I had a lot of work and didn't have time to try another update.
Today before update it I tried to install CCK and I get this error:

PHP Fatal error:  Allowed memory size of 16777216 bytes exhausted (tried to allocate 768457 bytes) in /var/www/www.xxxxxxxx.com/includes/database.mysqli.inc on line 303

And by now it's impossible to access to my site.
Luckily I have a backup.

So maybe the problem wasn't the View module, but something general!
But this is really odd! Why am I not more able to upload new modules??

#10

upupax - May 23, 2008 - 14:14
Status:active (needs more info)» fixed

Ok, I found my solution here

http://drupal.org/node/220261

Mark as fixed.

#11

hass - May 23, 2008 - 15:18

Theme developer module is one of the modules you should simple turn off. I tried it so often and it lock up your browser, lock up the PHP and so on an so on. Page loading with this module activated takes up to minutes with 100% CPU permanent load.

#12

upupax - May 27, 2008 - 12:59

I didn't have theme developer module installed, but I had memory problems as well..

#13

Anonymous (not verified) - June 10, 2008 - 13:04
Status:fixed» closed

Automatically closed -- issue fixed for two weeks with no activity.

#14

upupax - June 10, 2008 - 13:26

Just after you closed the thread it I discover where the problem was. I put this just in case someone has the same annoying issue.
The main problem was that View 6.x.2 Alpha5 insert the default frontpage view, that I already had.
This view is disabled by default, so it unpublished my previous content, and everything went "messed up" (images and menus disappeared).

#15

upupax - June 10, 2008 - 13:27
Status:closed» fixed

Sorry, I mark as fixed again..

#16

Anonymous (not verified) - June 24, 2008 - 13:32
Status:fixed» closed

Automatically closed -- issue fixed for two weeks with no activity.

 
 

Drupal is a registered trademark of Dries Buytaert.