I wouldn't even put this in beta. I just installed it (dropped it into folder and then enabled in modules). I clicked clone for frontpage module and now my entire drupal site doesn't work. I get page not found on every single page. I reapplied the drupal 6.2 folder but it still happens, which means something happened on the database.

Comments

vm’s picture

vm commented

clone for the frontpage.module ?

Did you test it on a test site first ? as a best practice ?

Beta doesnt mean Release Candidate and without you being an authority on this module and without you following best practices for deploying a new module, I think it's unfair to state whether you it should be beta or not.

Understand that quite a few people are using it without trouble and reporting bugs back in a civil, understanding and helpful matter.

stevenpatz’s picture

stevenpatz
he/him
commented
Status: Active » Postponed (maintainer needs more info)
merlinofchaos’s picture

merlinofchaos commented

Thank you, VeryMisunderstood.

k2xl: What version of PHP are you using? I'm finding that there's a lot of PHP4 problems showing up.

seanr’s picture

seanr
he/him
commented

Just had this happen to me too. Fucking lovely. :-/

Clearing the cache and disabling the views module via phpMyAdmin has no effect. We have PHP Version 4.3.9 (planning to upgrade, but it's going to be a pain in the ass for us).

seanr’s picture

seanr
he/him
commented

Add this after line 16 in index.php:

menu_rebuild();

Should be the first thing after the drupal_bootstrap line. Reload the page once, and then remove the line again.

seanr’s picture

seanr
he/him
commented
Title: Basically destroyed by drupal database » Views hoses the menu system, had to use menu_rebuild() in index.php to repair
seanr’s picture

seanr
he/him
commented
Priority: Normal » Critical
Status: Postponed (maintainer needs more info) » Active

BTW, gotta say this strikes me as fairly critical. LOL

merlinofchaos’s picture

merlinofchaos commented

I recently committed some fixes to PHP4 (i tested specifically with 4.3.9 and 4.4.7) -- seanr, can you cvs up and see if they still happen?

These problems don't happen with PHP5 and they also only happen in some circumstances, so they didn't get spotted in my initial poking (tho I admit I don't poke that hard at my PHP4 install)

seanr’s picture

seanr
he/him
commented

As soon as I try to re-enable views, it hoses the site again. Even with menu_rebuild in index.php, I just end up with a white screen until I manually edit the DB and disable views. So basically I can now no longer use views at all. Ugh. I'm not seeing erros in my server logs either, but after I disabled views, I ended up with a bunch of errors on screen:

* warning: 843 in /.../modules/views/views.module on line 843.

That's the foreach ($view->display as $display) in views_get_applicable_views.

seanr’s picture

seanr
he/him
commented

merlinofchaos - that seems to have helped. Thanks!

Please poke as hard as possible on PHP4 in the future - it's going to be a long time before most of us can get upgraded. ;-)

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

That is definitely the problem I fixed, then. It's in CVS. I'll roll a new release later today.

merlinofchaos’s picture

merlinofchaos commented

AS I understand it, there are security issues that make it very desirable to upgrade away from PHP4.

k2xl’s picture

k2xl commented

I would like to first apologize for the harsh words I used. I was just very upset at that moment, since I had to figure out which tables I needed to clear/delete (turned out just needed to clear the cache tables) and felt like blaming someone.

Anyway,
I have PHP4 right now. I would upgrade; however, I'm nervous to upgrade because I don't know how the rest of my website will be affected.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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