11
limecity
Re: disable caps on newbb title
  • 2010/5/12 5:28

  • limecity

  • Friend of XOOPS

  • Posts: 1602

  • Since: 2003/7/6 0


thanks bandidx
http://www.mounthiking.com
all your hiking gears and gadgets




12
limecity
disable caps on newbb title
  • 2010/4/29 5:42

  • limecity

  • Friend of XOOPS

  • Posts: 1602

  • Since: 2003/7/6 0


Hi,

I am very annoyed by some forumers who used CAPS throughout the forum title.

Is there a hack where I can force it to be uppercase letters to lowercase?

http://www.mounthiking.com
all your hiking gears and gadgets




13
limecity
Re: xoops chat integration (like facebook) ?
  • 2010/1/18 2:23

  • limecity

  • Friend of XOOPS

  • Posts: 1602

  • Since: 2003/7/6 0


very much looking forward to see that!. thats for the effort!



14
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?



15
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?



16
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?



17
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"




18
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?



19
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' ;



20
limecity
Re: xoops chat integration (like facebook) ?
  • 2009/10/8 12:58

  • limecity

  • Friend of XOOPS

  • Posts: 1602

  • Since: 2003/7/6 0


this could be integrated into the user account where the username can be click and msg instantly !

need to start learning php and sql now.




TopTop
« 1 (2) 3 4 5 ... 130 »



Login

Username:
Password:

Lost Password? Register now!

Who's Online

56 user(s) are online (27 user(s) are browsing Support Forums)


Members: 0


Guests: 56


more...

Donat-O-Meter

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

Latest GitHub Commits