I'd still look into some of the wrappers....

Such as the one in Content 0.5 module or SmartSection, just to name a few....

The content Module wrapping is basic and straight-foward...SmartSections is more versatile...(although I hear a new Content module is due out shortly...

I tried I-framing one of my php scripts and if the content of it overran I got scroll-bars all over the place!

The page wrap solved that...two cents...

I'd still like to know which it is for the block though....tags or no?

Or does eval add tags if it doesn't find them?

WHat module are you referring to, and what version of XOOPS are you using?

Did you look at the pages with debug turned on?

Did you read "Please read before posting" at the top of the forum....(better say no! )

Did you try uploading form.php from 2.0.14 to class/xoopsform/form.php?

Apparently there is an issue with form.php from 2.0.15...It corrected similar problems I was having in three different modules....

Quote:

Is there a database called XOOPS in mySQL? If not you need to create it so that XOOPS can then create the tables it needs within the database...AFAIK, XOOPS will not create a database for you, only add the tables it needs to an already existing database...

include/functions.php line 519


What is this line pointing toward? Obviously it is not finding what it is looking for and you may need to modify it.

Can you reinstall the old newbb? (last resort)

edit: Also, what versions are you using...XOOPS? Newbb?

Did you see this thread?

http_referrer error

Weird that it is something new after the upgrade was OK for a few days.....

Cache?

Did you try adding the www. to this?;

define('XOOPS_ROOT_PATH', '/public_html/domain.com/site2');

Seem like it is passing that to the browser and you get that weird redirect.

I don't seem to have that problem as my wehost uses a user name there instead of a domain name....

I'm getting this after running the update script (to 2.2.3a) on a 2.0.13.1 install....

Here's the difference...I've run the update on three installs with no trouble (in the end..LOL)...

But the fourth install, doing the exact same thing yeild the http_referrer error....

The difference? The fourth install is on a server that has a private SSL cert installed on it. It was installed on www.site.com, but I notice that XOOPS keeps stripping the www out and redirecting to site.com...and I get the error...

The tech that installed the cert suggested to put it under www.site.com...I email the servers support but I'm thinking their going to say it's a XOOPS problem...which judging by this thread I'm inclined to believe...:)

Is this a DNS issue? Or is it something in XOOPS?

UPDATE: Upon further investigation I find that XOOPS "works" as long as I stick with the site.com format URI...the second www is prepended the warnings start....on 2.2.3a

UPDATE2:

I tried switching authentication method to LDAP...now I'm locked out of the site because the LDAP module won't load...

I also installed to subdomain.site.com...works great!

The issue seem to be XOOPS NOT treating www.site.com and site.com as one in the same...

If I log into site.com...all is okay...while logged in if I migrate via the address bar in the FF browser to www.site.com...it wants me to login again. Which of course, it won't let me, because upon submitting the login I get redirected to site.com with a error message that it's the wrong password....

I think I'm just going to go baCK TO 2.0.13.2..disappointed.

UPDATE3: NAH, SCREW THAT! I'm going to make this work...it works on another domain install to webroot!

Any suggestions are appreciated...

UPDATE4: This appears to have corrected the situation somewhat...I'm not getting the http_referrer warning anymore....however if I attempt to login at site.com instead of www.site.com it doesn't know who I am...

This is from the FAQ;

"This could be caused by not having the XOOPS_URL and/or PHYSICAL_PATH in mainfile.php set to exactly where the website is located. This means that redirects do not work, as XOOPS checks the URL you logged into to the URL you are at, and if the base URL doesn't match (ie. www.xoops.org vs. xoops.org without www), you're not recognised as logged in."

Mine said "site.com"...it gave me http_referrer warning...I changed it to "www.site.com" (which matches a CNAME in my DNS) I no longer get the warning and redirect does indeed work now...that'll work for now...but there should be a way to handle that discrepency...imo.

Search "sub site" here and a thread will come up, someone wrtoe a module for it and hosts the download themselves...