Support Forum

Thank you so much for that filter. Unfortunately, I shouldn't have created a new theme before morning coffee. I used the Default theme and missed renaming default.php under styles. This now has caused an error loop I can't get rid off.

Here's what I initially did: I copied the default theme, added the filter to spFunctions.php, renamed the folder to default-mod, edited spTheme.txt and changed Theme Title to Default-mod, uploaded, activated. Bad mistake. At first things worked great. Then, upon logging out and trying to log back in, the entire site came up blank.

I immediately removed my default-mod theme. I could log in again. Going to themes under SP now yielded the following message:

Current Theme

The current theme stylesheet:

/problem-with-post-edit-buttonome/decor8sh/public_html/eclasses/blog/wp-content/sp-resources/forum-themes/default-updated/styles/default.php

cannot be found. Please correct or select a new theme for proper operation.

However, there was no other theme to select, it didn't even pull the still existing default theme.

In order to fix things somewhat I had to re-install my broken theme, activate it, then default became available again, activate that and delete default-mod again. Without deleting default-mod the forum wouldn't work at all.

So now I've created a new theme called default-edited, making sure I rename default.php to default-edited, uploaded, activated - and was presented again with:

Current Theme

The current theme stylesheet:

/problem-with-post-edit-buttonome/decor8sh/public_html/eclasses/blog/wp-content/sp-resources/forum-themes/default-updated/styles/default.php

cannot be found. Please correct or select a new theme for proper operation.

Every new theme I've tried creating since comes back with that one error message. The only theme I can now use is default. Very sorry about this but how do I start over?

A minor detail perhaps but I think it's worth mentioning: I had to click Activate Theme twice (sound familiar?) to activate my edited theme. Though I only had to click once to make Default active again.

Also, checked my error log which pointed me to sf_errorlog. So I did one more theme switching and this is what shows up in sf_errorlog at the same time:

file: /simple-press/sp-startup/site/sp-ahah-handler.php<br />line: 21<br />function: Unavailable<br />Warning | Cannot modify header information - headers already sent by (output started at /problem-with-post-edit-buttonome/decor8sh/public_html/eclasses/blog/wp-content/sp-resources/forum-themes/default-updated/templates/spFunctions.php:55)

Thank you, that was the issue. There was a white space after the closing tag. Removed that and tried again - now it works.

For the time being I have removed tinymce from the signature box. This works well as the tutorial video I put together for the students was done with a previous version of SP that did not have this feature.

This buys me time to do focused troubleshooting once class concludes. If all else fails I might just have to wipe my install and do over with a clean one.

Thank you again for all your help, very much appreciate it.

Yes, I did. I removed google jQuery and deactivated tinymce advanced. I also deactivated a few other plug-ins afterwards. No matter what, it didn't help. I even switched to the Twenty Twelve WP theme while tinymce advanced was deactivated.

I am rather confused at this point. Especially since now that I created a modified theme I suddenly have to click Activate Theme in SP twice before it takes. If you still have the login I provided feel free to give it a go and see what I mean. My error_log says the following upon switching themes:

PHP Fatal error:  Cannot redeclare spdefault_textdomain() in /problem-with-post-edit-buttonome/decor8sh/public_html/eclasses/blog/wp-content/sp-resources/forum-themes/default-updated/templates/spFunctions.php on line 30

I see. That part was listed as not mandatory though it does go on to state that if not done it may lead to error messages when switching themes. Perhaps it should be mandatory then. In any case, that's all set now. No more errors.