SimplePortal
Support => English Support => Topic started by: Burke Knight on December 31, 2014, 02:18:02 PM
-
Method Not Implemented
GET to /index.php not supported.
This is what I get, when I try to edit php blocks.
This happens even on a fresh install, now.
-
You state this occurs on a fresh installation of what in particular, do you mean after a fresh SMF installation?
I do not think this is a SimplePortal issue as it seems to be related to server configuration.
Was anything changed recently within your server configuration?
Perhaps something in your php.ini file, filer ownership/permissions or a .htaccess file?
Regards.
-
Nothing changed.
Had done fresh file install of SMF and all mods.
However, it only seems to do this on some php blocks. Not all of them.
Yet, never had this issue before.
-
Did you install a particular SMF modification or plugin just prior to this occurring?
-
Nope. Same order it was all in on the old site.
Also, now getting this in the error log:
http://www.burkeknight.com/index.php?
8: Undefined index: avatar
File: /Themes/default/languages/Post.english.php (portal_above sub template - eval?)
Line: 183
-
Nope. Same order it was all in on the old site.
BurkeKnight,
With that statement can I assume you have migrated to another host?
If this is the case then perhaps you have a misconfiguration of some sort as I have previously suggested?
Perhaps this is a path issue due to the migration which can be fixed with the repair_settings.php tool available at SMF.
Regards.
-
No, I have not migrated to another host.
If did that, would have just moved the site.
I wanted to clean things up, get rid of extra files and such, from old mods, etc that were left over through the years, as well as do it as a clean 2.0.9 instead of 2.0.4 with all the updates.
And it is not a path issue that can be fixed via that, as that is how I moved from dev site, to main site, and would have fixed it.
-
BurkeKnight,
So you recently ran an upgrade? When the forum was fresh without any mods installed did you remove all the hooks from the database using the repair_settings.php tool? (<-- only do this when no mods are installed)
-
Okay, let me repeat... The install was a clean install of 2.0.9 and then t5he same mods, same order as the original site. When imported the database, I did run remove hooks, before I installed the mods.
However, the first issue, is sporadic. I notice it at times on the blocks, yet at other times, I can modify them.
Unknown what it is, but this is not the only site have had it happen on. Had it on a couple test sites, also.
It also happened in a 2.1 test site, using the SP made for 2.1 I found on GH. ;)
The second issue, I really have no idea about, as this is the first I've seen of that error. But, since it stated portal in it, I figured I'd post here about it.
-
The error stated portal in it because it uses the portal files to display the blocks on the page (whether blocks are present on the page or not).
Wipe your error log, then go to your Server Settings and disable evaluation of templates which should then point you to the proper file for that error.
Also... Are you absolutely sure you installed all your custom templates first prior to installing the mods to ensure the mods would make alterations to all template files when necessary (by checkboxing during their installations when applicable)?
Ensure to run the following maintenance tasks:
Empty the file cache, Recount all forum totals and statistics, Find and repair any errors and Database -> Optimize all tables.
You can also try adjusting Use database driven sessions in your Server Settings.
From what I have read thus far on this error, it appears to be related to the app named mod_security which your host has installed
(or you installed it if this is VPS/Dedicated).
-
If your hosted account is managed then you can relay the error to them and ask them to adjust mod_security to fix the issue.
If it is unmanaged VPS/Dedicated then at this time I am not positive how to adjust the issue although you can probably get some info on an Apache site or perhaps your OS main site forum (ie. CentOS or Ubuntu).
You can add code to your .htaccess file to turn mod security off if you wish to do that.
<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>
ref. http://stackoverflow.com/questions/12928360/how-can-i-disable-mod-security-in-htaccess-file
-
You may be able to adjust Mod Security via your web hosting control panel (ie. CPanel).
Have a look at this link for more information: Click Here (https://documentation.cpanel.net/display/EA/Apache+Module:+ModSecurity)
-
1. I am only using the default theme, copied, and yes, before installed the mods.
1.a. The 2.1 only used the default theme.
2. Mod_security is not the issue. I run my own server, and that nwas one of the things I dealt with, way back when first started the server....LOL ( I would NEVER install it myself, with all the issues it causes...LOL )
EDIT: I just checked, and somehow, it had been re-enabled. Must have been an update on the servers, but I disabled on all domains, again.: Successfully disabled ModSecurity™ on all domains. However, error still goes.END EDIT.
3. Disable evaluation of templates just changed the error to display: PortalShoutbox.template.php instead of what was before.
4. Use database driven sessions is how it's been set up.
-
You have to reset Apache after you disable Mod Security.
-
No, I do not.... Never had to before, and that is only on some setups that would.
However, I found the cause of the error. Seems when had copied some code in my new look for the shoutbox, it still had the code from the avatar mod for the shoutbox.
Which, that mod will not work in the latest SP, for some odd reason.
I removed it, and the error is gone. Would never have found it, though, if it did not finally tell me it was the shoutbox template....LOL
-
I am glad you found the issue.
No, I do not.... Never had to before, and that is only on some setups that would.
Every change to your Apache configuration needs an Apache restart (<-- specifically).
ie.
sudo service apache2 restart
Imo removing the leftover code from the avatar mod solved your undefined index error but it was the disabling of Mod Security and restarting Apache that probably solved your Method Not Implemented error. The 2 errors were not related.
Regards.
-
I am glad you found the issue.
Every change to your Apache configuration needs an Apache restart (<-- specifically).
ie.
Imo removing the leftover code from the avatar mod solved your undefined index error but it was the disabling of Mod Security and restarting Apache that probably solved your Method Not Implemented error. The 2 errors were not related.
1. This solves the errors in the error log, not the original issue with the title of this topic.
2. Not every change, as changing the mod security is done via cPanel, and does it without needing a restart. I have this backed by 5 server admins of various web hosts. I had once thought like you did, until they set me straight, via demonstrations. The cPanel way is a lot easier to deal with. However, you do need to restart if using the command structure to do so.
3. I had the errors showing and not showing before and after disabling. If it was mod security, I'd have gotten a blank page or the typical 500 error. ( Which had to fight a lot on a friend's site recently, until she moved her site....LOL )