I feel sure you didn’t really mean that 700+ users ALL tried to edit their signatures yesterday…

On the subject of the Advanced TinyMCE plugin – an explanation. All WordPress TinyMCE extension plugins I have encountered are aimed at adding extra buttons/functions to the creation of blog posts. This means they are used exclusively in the Administration – NOT the public facing site. However – there is a habit for them to be loaded on the public facing site as well. This is bad coding of course. And it is made worse now since the WordPress team made it possible for other plugins (like SP) to make use of the WP supplied TinyMCE because such bad loading is most likely to cause conflicts. This can usually be corrected with a very simple change.

Now to your site. Having taken a look there are some other issues which may well be relevant to all of this and which, in any case, would be best cleaned up as we can only really diagnose a specific issue when there are no other conflicts showing up.

This codex article explains a problem your site has, what this means and what to look for: http://codex.simple-press.com/codex/faq/troubleshooting/what-is-this-jquery-conflict/

In your case something – I suspect the theme but it may not be – is loading a very old (1.4.1 as opposed to the WP required 1.8.3) version of the main jQuery library. This is also being loaded from the googleapis.com CDN and is loaded not using the WP API so later, the proper version is also loaded. This can cause all sorts of unexpected and inexplicable problems and is, basically, plain bad.

Well, certainly not all 700+ at once – but quite a few. As they all paid to take the class my main concern is that everything works perfectly well. If it doesn’t I get a bit uneasy (and of course, one issue tends to bring a bunch of friends).

I actually had read the codex article you posted this past hour, doing some more research here on the forum. I noticed too that the current template (via header.php) loads a jQuery library from Google. I was hoping this would be the root of my issue. Unfortunately it was not. I switched to the basic Twenty Twelve template but it did not resolve the issue. Though on a side note I will contact my theme developer to take a look.

I even went as far as deactivating ALL plug-ins except SP. That didn’t help either. I also re-installed WordPress, just for the heck of it.

For sanity reasons I’ll summarize: tinymce causes a problem solely on the signature box (the post box works perfectly fine). If tinymce SP plug-in is deactivated the issue goes away. I tried switching WP theme to basic theme. I tried disabling all plug-ins. I tried re-installing Worpdress. And I tried re-installing SP. I suspected TinyMCE Advanced though deactivating it didn’t resolve the issue. I also suspected my current themes jQuery thus switched to the basic WP theme. Still no go.

Admittedly it is not a site breaking issue. But it is of concern and it is something that requires explaining to a group of students primarily composed of beginning to intermediate bloggers from the creative world. And of course, Murphy’s law: anything that can go wrong will go wrong (once it starts).

FYI, I commented out the Google jQuery call in my current theme. It should’ve been disabled anyway when the theme files were recently modified for our needs by an external vendor.

But the signature still won’t save after removing the Google JQ?

We are also looking at the double click deal on “Edit Signatures” but that won’t affect the saving it part.

earlier, you asked about turning off tinymce on profile…

you should be able to add this to you spFunctions.php file (make sure its your own and not one of ours)…

add_filter('sph_this_editor', 'my_editor_check');
function my_editor_check($editor) {
    global $sfvars;
    if ($sfvars['pageview'] == 'profileedit') $editor = 4;
    return $editor;
}

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?

Right, I’ve taken a stupid pill. So I missed another thing, rename Stylesheet: Default in spTheme.txt. Scratch all that previous blah blah, I did RTFM thoroughly now (yes, it’s easy to follow).

Now all is well again with the themes.

But, adding your filter into my new, correctly modded, theme still causes the entire site to come up blank once I log out. While I am logged in everything is fine. Log out > site goes blank. So then I have to remove my modded theme via FTP, log in, go to SP themes, get error message, no default theme available to chose, need to upload my modded theme again and now I can see default as well and activate that. Then delete modded theme. Right. Aside from a lot of unnecessary words from my side (RTFM) and excellent replies from yours I am still stuck.

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)

The error message suggests a problem with your coding in the function template file. Where and how did you add the code? If at the end of the file – did you leave any white space after the closing php tag because that can cause issues like this… Or – conversely, if you added it at the top you must leave no trailing space before the php tag. Could that be it?

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.

Ah good. It is a common and misunderstood error.
By the way – did you ever actually try with the google jQuery gone AND the advanced plugin deactivted at the same time?

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

That error is because you have not altered the name of the text domain (for translations) to match your custom theme. I believe that covered is in the custom theme instructions. It will only occur when you activate a different theme with the same text domain name (i.e., ‘spdefault’).

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.

if you didnt have the default theme, it wouldnt be mandatory…    some users remove the themes they are not using… but still, a fair statement…