Support Forum
Support Forum
Offline
I have a multisite install of Simple Press 5.5.0 on WP 3.9.2 running Sterling theme
On all but one of the subsites the TinyMCE icons in the editor do not show.
I have tried to figure out the difference but cannot. All the settings seem to be the same.
I have tried reinstalling SP themes, switching themes, I have tried on notebook, tablet and smartphone and it is the same.
There were some issues with the Integration with a couple of the subsites where Forum CSS/JS Cache was pointed to the wrong place. I created a folder where it should be and the Integration error went away, but still no icons. Yet the one subsite works fine....
Where should I be looking??
Offline
I don't have any experience with subsites unfortunately, but just starting with the basics..
Do subsites allow their own WordPress plugins? or is one plugin activated across all subsites. If individually, is there a possibility you having something running on the sites with the issue, that you don't on the one that is OK?
Are you getting any errors in the console on the subsites with the problem?
Is this a new issue? or has your editor been missing the icons for a while.
Sorry it's a bit vague at the moment.
Offline
And when you refer to 'settings' being the same, does this include the editor tinyMCE settings under components?
 |
YELLOW
SWORDFISH
|
Offline
remember, each network site install is unique with essentially no tie to any other install... so as Andy asks, make sure you have the settings for the site and simple press as desired...
can you elaborate on the changes you made to the combined css and js cache locations? if that was an issue, it still may be... perhaps try disabling the caches on forum - options - global settings....
Visit Cruise Talk Central and Mr Papa's World
Offline
I have methodically compared two subsites (one that works and one that doesn't) and all the settings, including the TinyMCE settings in Components are identical. Both are set to use a plain text editor, but changing that to use Rich Text (TinyMCE) editor does not change the way that the editor displays... Not sure why. Do I need to log out and log in again to see the change??
Simple-Press seems to still try to use blogs.dir to set itself up on a multisite, but that directory doesn't exist, so when I set it up on a new subsite I have to manually create the directory, unzip the two resources files and edit the Integration file locations. It's possible that in this manual process that the files did not all propagate properly.
Where specifically are the editor icon image files located? If I know that, I can make sure that they are in fact there!
Offline
Are we really talking about tinyMCE with no icons? Or are we really talking about no tinyMCE editor at all? Can you put the cursor into the edit window and type text? And while asking questions - are all of these sites running identical WP plugins and themes?
|
YELLOW
SWORDFISH
|
Offline
Yes the editor works fine, and the links are all there for the buttons, and the descriptive text pops up when you mouse over them. The links all work for Bold, Italic, etc, but there are no icon images to tell the user which button is which. So I think it is either pointing to the wrong place or the icons are not where they are supposed to be. See screenshot below:
Offline
Ah. Sorry. I had misunderstood the problem. OK - so lets start with the story!
In version 3.9, WordPress adopted version 4 of the TinyMCE editor from Moxie. One of the things this included was ceasing to use the old icons for the toolbar and replacing them with a font set of glyphs. If your toolbar works on the WordPress Post and Pages then you will be seeing these. This change was a major shift.
Some plugins that add functionality to the editor toolbar were not updated to take this change into account which can cause the sort of failure you see here. Some plugins that add functionality incorrectly assume that the editor can only be used in the backend, administrative side of WordPress. They will use the WP API to instantiate the extra toolbar buttons and functions but do say in a way that affects both back and front ends without loading the code for the front end. This too can result in the sort of problem you see.
The final problem that can manifest itself in what you see is if the WordPress/SImple:Press/SP TinyMCE plugin are not all using the most up to date versions.
Now - looking at the screen shot you attached I can see that you DO have some sort of plugin adding a lot of items to the TinyMCE toolbar. i would start by simply deactivating that to see if that is the culprit.
|
YELLOW
SWORDFISH
|
Offline
OK. I've gone through all the SP plugins and made sure the exact same ones are activated (and the same version) on the subsite that doesn't work as on the subsite that works. Ditto with the WP plugins. I turned off any extras one by one and reloaded the "Add Topic" page each time and still no glyphs. The WP blog editor works fine on both sites. I turned off TinyMCE Advanced 4.02. Updated to SP 5.5.0.1 Tried turning off the CSS/JS Cache.
Is it possible that due to the glitches in the install with having to create new folders, etc that there is a SP file missing? Which file points to the glyphs' location? I assume SP uses the WP glyphs and not its own set...
Any ideas for a next step? Any common culprits to look for? Could it be a missing CSS file?
Offline
all the icons are located with the sp tinymce plugin- they are a set we deliver with the pliugin, not the wp ones... so if it loads on any one site, the icons are there... there is not a unique install per network site - just the single install... which indicates some kind of permission or path issue from the network site to the location of the plugin...
if you inspect the css for the icons, you should be able to see where its pointing and see if that file is accessible...
are you using any kind of domain mapping plugin? or a security module (apache or wp) that might be blocking one of the network sites from accessing a file in the main site?
Visit Cruise Talk Central and Mr Papa's World
All RSS1 Guest(s)