Support Forum
Support Forum
Offline
if I chose the plain text mode for writing it all works.
if I chose rich text tinymce it looks like this: http://screencast.com/t/YQic9yV9 but you simply can't click into the field where you are supposed to write.
if I chose plain the bbtext version clicking on reply brings this up: http://screencast.com/t/odLlcXr7
Btw. I have re-uploaded all plugins, no problems this time. I double checked my permissions and ownerships but they are all ok. Its my own root server so I checked via ssh console and its all ok. Wordpress can edit/delete/upload files and that indicates everything is alright.
Offline
This suggests javascript conflicts. Can you run this with the error console or the firebug console to see if any errors are reported when you try top load the editor?
 |
YELLOW
SWORDFISH
|
Offline
sure: http://screencast.com/t/F8sdebFx for tinyMCE and this: http://screencast.com/t/MAaiifMn for bbtext
does that help?
Offline
would you be willing to very briefly switch your site to use the default WP theme just to determine if things start to work as expected?
If they do switch right back.
If they do not perhaps you could then briefly deactivate the wp-wall plugin and try it again...
Possible?
|
YELLOW
SWORDFISH
|
Offline
- switched to tinyMCE for SP
- switched to default WP theme
- deactivated WP Wall
- tried posting, same problem
BUT I found the culprit: http://wordpress.org/extend/pl.....braries/
Would you mind having a look? That is a very useful and widely used plugin, I am wondering why it breaks SP. Shall I ask that author too or will you check it out first?
Offline
Oh I didn't even know about this plugin. I assumed your theme - or wp-wall - was sourcing them from google which is the only reason I asked you to make the switch.
This forum is littered with this little speech but here goes again!
- As many people will dispute the profit of using the google cdn as will support it. If there is any gain using it over the supplied WP versions - the first time you visit a site - then we are talking nanoseconds. Note the Wp supplied versions are, of course, also compressed.
- To load jQuery and the jQuery UI from the google cdn you have to specify a version. As many theme and plugin authors embed these calls into their code they often do NOT update them for each new version of WP which ALWAYS uses the latest. So we see a lot of incorrect versions being loaded.
- Most importantly, the Wp supplied version of these libraries use the 'no conflict' mode. The google sourced versions do not. This means that any plugin written to support Wp properly (like SP) can fail. It also means that a user who might be using a plugin calling, say, the prototype library, will immediately have a conflict and failure.
we do now specify in out system requirements (http://codex.simple-press.com/.....uirements/) that the correct and supported versions of jQuery libraries are needed for SP.
|
YELLOW
SWORDFISH
|
All RSS1 Guest(s)