XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. 2.4.x Support 
  4.  / admin blank after upgrade from 2.3.3b to 2.4.3
Register
1
limecity
admin blank after upgrade from 2.3.3b to 2.4.3

  • 2010/1/15 21:25

  • limecity

  • Friend of XOOPS

  • Posts: 1602

  • Since: 2003/7/6 0


after all the upgrade which i was notified successful,

tried login to the site it was all ok.
but when login to the admin.php.
the site went blank.

tried to troubleshoot, I disable the protector module through the database directly and it then I can login to my admin.

and I can't see the protector module at all from my admin. it also gives a weird and uncompleted load looks of the admin when I load the admin page like the image below

Resized Image

what do I do now? how should I uninstall / reinstall a installed protector which is not visible from the admin?


*update* after some module update.
i enabled the protector from the database again. and tried to login to admin.php. it showed

"Registry not found"

just extra information. i have 2 protector folder. one in the module section and another one in the trusted path side. is that correct?




Other Question:

do i need to include these 2 lines back into mainfile.php after the upgrade ?

include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ;

include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' ;
2
Mamba
Re: admin blank after upgrade from 2.3.3b to 2.4.3

  • 2010/1/15 23:26

  • Mamba

  • Moderator

  • Posts: 11366

  • Since: 2004/4/23


Quote:
just extra information. i have 2 protector folder. one in the module section and another one in the trusted path side. is that correct?

Correct. Just make sure that there are no other protector directories. Sometimes people have one in their "old" trusted path, and then they have it in /xoops_lib that they copied as part of the XOOPS Update. Make sure that the content of /xoops_lib is in your "trusted path" folder

Quote:
Other Question:

do i need to include these 2 lines back into mainfile.php after the upgrade ?


No, in 2.4.3 there is no need for it anymore (please read release/installation instructions about it)
3
limecity
Re: admin blank after upgrade from 2.3.3b to 2.4.3

  • 2010/1/16 5:00

  • limecity

  • Friend of XOOPS

  • Posts: 1602

  • Since: 2003/7/6 0


i still can't get into admin when enabled the protector from the database.

any pointers on what i should do now?
4
Burning
Re: admin blank after upgrade from 2.3.3b to 2.4.3

  • 2010/1/16 5:10

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


hi'

Clean :
• _sessions table
• xoops_lib/modules/protector/configs (except index.html)

Make sure that xoops_data and xoops_lib folders are right chmoded (opened for writing)

Tell us
5
limecity
Re: admin blank after upgrade from 2.3.3b to 2.4.3

  • 2010/1/16 5:40

  • limecity

  • Friend of XOOPS

  • Posts: 1602

  • Since: 2003/7/6 0


hmmm just done that.

still get this "Registry not found"

6
Burning
Re: admin blank after upgrade from 2.3.3b to 2.4.3

  • 2010/1/16 5:55

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


Sorry, I haven't seen this alert

In this topic, user said that problem cames from bad mainfile.php configuration : here

So, I believe you have to check path (withou trailing slash), especially root_path wich goes to xoops_lib
7
limecity
Re: admin blank after upgrade from 2.3.3b to 2.4.3

  • 2010/1/16 6:51

  • limecity

  • Friend of XOOPS

  • Posts: 1602

  • Since: 2003/7/6 0


i redo my mainfile.php by using the mainfile.dist.php from 2.4.3 but still doesn't work either.


// Physical path to the XOOPS documents (served) directory WITHOUT trailing slash
define("XOOPS_ROOT_PATH", "/home/xxx/domains/xxxdomain.com/public_html");

// For forward compatibility
// Physical path to the XOOPS library directory WITHOUT trailing slash
define("XOOPS_PATH", "/home/xxx/domains/xxxdomain/xoops_lib");
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash
define("XOOPS_VAR_PATH", "/home/xxx/domains/xxxdomain/xoops_data");

what else can i do?
8
ghia
Re: admin blank after upgrade from 2.3.3b to 2.4.3

  • 2010/1/16 9:54

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


Do the file check (see release notes).
(If the xxops_lib and xoops_data files are listed as error, make temporary a copy from xoops_lib and xoops_data (from the server) to /public_html/)

Are the directories in good order (having eg /home/xxx/domains/xxxdomain.com/public_html/mainfile.php and /home/xxx/domains/xxxdomain/xoops_lib/modules/protector/xoops_version.php)?

You have also the definition of
define("XOOPS_TRUST_PATH", XOOPS_PATH);
in mainfile.php?
9
limecity
Re: admin blank after upgrade from 2.3.3b to 2.4.3

  • 2010/1/17 0:38

  • limecity

  • Friend of XOOPS

  • Posts: 1602

  • Since: 2003/7/6 0


already had the trusted path defined in mainfile.php.
now i can access the admin with the protector turned on.
but the module pages in admin still turn out weird and protector is no where to be seen.

I think i willl try to reinstall the upgrade.

Can i delete the stuff in the xoops_cache, smarty_complile and smart_cache? in the trusted path?

I see alot of forum uploads files from inside XOOPS cache. are those just cache files?
10
limecity
Re: admin blank after upgrade from 2.3.3b to 2.4.3

  • 2010/1/17 11:25

  • limecity

  • Friend of XOOPS

  • Posts: 1602

  • Since: 2003/7/6 0


still unable to login to admin with protector.

i download XOOPS full package and replace the necessary files. checksum verified all the files are correct.

can XOOPS 2.4.3 run without protector? if so, can i remove protector clean from the site? and make a fresh install of protector?

how do i do that?
(1) 2 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

122 user(s) are online (89 user(s) are browsing Support Forums)

Members: 0

Guests: 122

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits