Phpnuke 7.6 patched 3.0 conflicts with Autotheme lite .8

New Member Joined: Jun 10, 2005 Posts: 6

Phpnuke 7.6 patched 3.0 it conflicts with autotheme lite .8
It shows blank page in IE and on Firefox gives this error : Too many redirect ... or something like this.
Is there any fix for this ?

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

The message is probably "Redirection limit for this URL exceeded".

A couple of things to try. First of all, delete your cookies and clear your cache. Did that fix it?

In general, this would be the situation that would legitimately cause this error. In file1.php, you would have a header("Location: file2.php"). File2.php has some fuzzy logic that tells it to call header("Location: file1.php"); That's where the limit is reached because of the loop.

That would not be the only way. There could be a mod_rewrite directive that is looping. Try temporarily renaming your .htaccess file to see if it clears up.

Posted: Sat Jun 11, 2005 12:05 pm

I thought too about the cookies and tried that. It doesn't work.
I also dont have .htaccess as I didn't yet installed the sentinel.

I've droped the issue also on autotheme site and the owner said he tried to copy the patch 3.0 file by file and it stoped working until he copied the following blocks:

block-Languages.php
block-Modules.php
block-Who_is_Online.php

I had a look ove those blocks but didn't see the reason. Maybe it explains more to you.

And thx for reply Razz

Really appreciated.

Posted: Sun Jun 12, 2005 8:53 pm

A few things.

1) Are you running from a sub-domain or in a sub-directory?
2) Regardless of where you are running, you should have some basic .htaccess rules about your domain. When I say basic, the first thing after "RewriteEngine on" should be:

Code:

Rewritebase /

My experience has been that people run into this problem when their DNS files don't match the domain where the base installation is OR when DNS wildcards are used for sub-domains. In the latter situation, it's really a CPANEL issue, but it does exist. In that situation, you should really remove the * wildcard and add all of the sub-domain information manually repeating all of the setting for your primary domain for the sub-domain. What I mean is the mail, ftp, cname, etc... information for the sub-domain.

Finally, I've found other situations where people are using"

Code:

RewriteCond %{HTTP_REFERER} http://yourwebsite.com

AND

Code:

RewriteCond %{HTTP_REFERER} http://www.yourwebsite.com

This is problematic as it can also create loops in certain circumstances. Really, all of that should be difined in the DNS controls and after once that is setup, you'd define specific settings for subdomains such as:

Code:




Rewritebase /


RewriteCond %{REQUEST_URI} !^/SUBDOMAIN/


RewriteCond %{HTTP_HOST} ^(www\.)?SUBDOMAIN\.


RewriteRule ^(.*)$ SUBDOMAIN/$1 [L]

NOTE: SUBDOMAIN = the name of the sub-domain in question.

It has been my experience that if you are getting the error:

Not having these essential settings is why.

Hope this helps!
Steph

Posted: Tue Jun 14, 2005 12:01 pm

Thanks for help. That didn't worked though Sad

Posted: Tue Jun 14, 2005 1:40 pm

Please PM me your
Site url, god adminid/pass
FTP url, id/pass

I will take a closer look when I get time.

Posted: Tue Jun 14, 2005 2:32 pm

I was going to look at this too if you wanted, but wondered.

What version of patched? 3.0b?
Also, you say it "Stopped" working until certain files. Do you mean the other way around?

Can you post the link to the support thread at autothemes?

Thanks
Steph

Posted: Tue Jun 14, 2005 2:40 pm

Steph, I would appreciate it if you could handle this. Yav, please work with Steph. Thanks!

Posted: Wed Jun 15, 2005 10:32 am

Here it's the autotheme suport forum link : http://spidean.mckenzies.net/SpideanForums+viewthread-tid-3459.phtml

Thanks for involving into this.
I was reinstalling my site from scratch because of the security problems in 7.7 and 7.8
So I've installed a fresh 7.6 then applied the 3.0b patch. After that I installed autotheme. At the moment when I've tried to set the autotheme theme as my theme I got the "Redirection limit for this URL exceeded" message and error.

Let me know what you need from me Seth to find the problem. I can find a way to give you access to the site. My site is : www.colloseum.ro

Posted: Wed Jun 15, 2005 12:02 pm

I sent you a PM.

Thanks
Steph

Posted: Thu Jun 16, 2005 9:29 am

This definately looks like an autothemes issue.

If everything works when using any Nuke theme, but not with autothemes, either there is a missing or changed variable in the configurations of autothemes or a permission is set wrong.

I'm not really surprised by this situation given that they don't know what the "Patched" series of updates is.

Keep in mind that autothemes has not been updated in over a year and has failed to follow Nuke Development, so there could be a variety of reasons why you are having issues.

I would suggest also that the person who was testing "Patched" was testing it incorrectly. You wouldn't start by uploading those 3 blocks and saying, "Wow... It doesn't work now".

That's not the way that "Patched' works. Its files must be uploaded and it must be "Run" to execute the the database update. Then you would re-install the Autothemes solution from there.

Now, that is not to say that some things don't function after a "Patched" update. Remember that we are overwriting Nuke Files and thus, we may need to go back and "Re-Install" things like Autothemes.

That being said, most of the time, it is a matter of:
1) Following the "Patched" methodologies for access administration and forums administration screens (see the "admin ==" issue as well as the includes.
2) Following the "Patched" methodologies for accessing database tables (Secured versus nuke's default methods not being secured)... This means never a dbi call.
3) Use of $module_name and having those values used in globals.
4) Other patched fixes and revisions.

I would suggest going back and carefully examining the Autothemes installation process. I would re-install autothemes as if it had never been done before.

Personally, my suggestion would be to not use autothemes in the first place for a very large and wide variety of reasons, but if you feel that you must, I would nail this down by starting from stratch and having the autothemes people read this forum thread and do the same in THEIR testing.

Posted: Thu Jun 16, 2005 12:21 pm

It's ok. I'll switch to another nuke theme.

The thing I'm sorry is that I payed 35$ for an autotheme instead of donating to you guys.
And again thanks for your involment.

Posted: Thu Jun 16, 2005 12:29 pm

Well, before you write it off, you might want to go through the installation process again and see if anything is missing.

Again, I would also point the autothemes support people to this thread so they at least know that:
1) You install nuke
2) You install patched
3) You install autothemes

Posted: Thu Jun 16, 2005 2:49 pm

Ok. I'll do that.

Btw. I just saw that they are listed in the parteners section.

Posted: Thu Jun 16, 2005 3:10 pm

I think they advertise here.

New Member Joined: Jun 23, 2005 Posts: 1

I'm using nuke 7.6 with the patched 3.0 too.
Also I'm using AT-Lite 0.8
I've been able to get past the URL redirection problem by adding the following code.

In /modules/AutoTheme/includes/php-nuke/atAPI.php file add the following code :

In "function atBlockLoad" right after "$prefix = $GLOBALS['prefix'];" I added :

Code:




if(!defined('BLOCK_FILE')) {





define('BLOCK_FILE', true);





}

I don't know if that's the correct spot to insert the code, but it looked about right and works.

Now my main pages load, but I'm missing my right blocks
Still looking into that.

chilimonkey

Posted: Wed Jul 13, 2005 8:25 pm

Any luck with those right side blocks? I'm running into the same problem with Platinum...

Posted: Thu Jul 14, 2005 1:07 pm

Ok I'm guessing no one has yet. I'm going to skip this for now as we're in the middle of setup and its just easier to go to a standard theme. Though AT has some features we would like to work with its just not worth spending hours on for us at this time.

Involved Joined: Jul 12, 2005 Posts: 283

Just as a FYI. I have php-nuke 7.5 with sentenial and 3.0b patches installed, and i tried to installed autotheme .8 and it didnt work, totally disabled my site.

The makers of autotheme are of no help!
Smile

New Member Joined: Jul 17, 2005 Posts: 1

Same problem here, just post to keep track of this thread...

Client Joined: Aug 11, 2005 Posts: 32

Looks like we are screwed for the time being. Both sides are saying talk to the other:

Quote:

Patch for a PHP-Nuke vulnerability or a chatserv vulnerability (I assume that chatserv is a module)? PHP-Nuke did not release this patch AFAIK, so maybe the chatserv folks would be kind enough to fix their patch so that it doesn't break AutoTheme and your site. Drop them a line and let me know.

Thanks!
-Shawn

Posted: Fri Aug 12, 2005 10:10 pm

I no longer recommend nor endorse that product due to some shady business practices of his that I have become aware of. For him to pretend that he doesn't know who Chatserv is is even more testimony to his lack of professionalism! He not only does not support his product but according to a client of mine, he (Shawn) sabotaged a client's nuke installation with the login information that he was given in trust.

Posted: Fri Aug 12, 2005 10:13 pm

Well d***. Thanks for the heads up. The only reason I installed autotheme was because It was required to use the custom theme I bought and paid for. Now I don't know what to do. I wish I could get this theme to work without autotheme. Any ideas?

Admin Note: New thread opened at http://www.ravenphpscripts.com/postx6391-0-0.html

Posted: Fri Aug 12, 2005 10:25 pm

I don't see anywhere that you've posted what the problem is.

Posted: Sat Aug 13, 2005 12:38 am

lol the things one misses, so i'm a module now? it's nice to place the blame on something else when the fact is the product has not been updated in ages and naturally has fallen behind Nuke's current structure, Nuke is getting many variables turned into defines, does this break old add-ons? of course, but these are long overdue changes IMHO. I for one do not use auto-theme but have seen its files in the past and they alter how Nuke handles the themes completely and since its code is broken into many files making required changes would be a pain as far as i can see, the author should state at his site that his product is only intended for Nuke 7.4 and older as 7.4 dates back to the summer of 2004, so if they haven't updated in over a year that's the newest version of Nuke their clients could use if at all, they should also warn clients that their product is not intended for Patched Nuke sites.