PP Editor Not Appearing After Upgrade to PP 0.19
Sat, 02/05/2009 - 18:37
After upgrading to PP 0.19. the PP Editor does not appear anymore. I use TMA Custom Theme. Any idea where I should reset the PP Editor functionality?
__________________
Sat, 02/05/2009 - 22:11
#2
PP Editor is Ok with TMA2 but not with TMA Custom Theme
Thanks for replying Beng. PP editor functions perfectly in my other sites that use TMA2 but not in my one site that that uses TMA custom (the one that links to my signature)---www.voxbikol.com. All these sites have been upgraded to PP 0.19. I already cleared the cache (in Performance menu and Mozilla's Tools menu) and I even removed tha latest Drupal modules that I installed (Fivestar and Create Related Content), but the problem is not solved.
__________________
Sat, 02/05/2009 - 22:53
#3
The theme should be
The theme should be unrelated, but if you want, you can try switching from tma_custom to tma2 and see if that changes anything.
When the editor doesn't appear, are you editing a node or story? Or a comment?
Are you logged in as the first user? Or as an editor user? Or a staff user?
Also, can you check your permissions settings (at .../admin/user/permissions)? Look especially at the permission access ProsePoint editor.
And, can you visit .../admin/settings/performance and set Optimize JavaScript files: to Disabled?
Sun, 03/05/2009 - 10:52
#4
The PP editor is only disabled in TMA Custom theme
Beng,
The PP editor is only disabled in TMA Custom theme, so when i add or edit a story I switch temporarily to TMA2 theme then back again to TMA custom when done. Optimize javascript file option is also disabled; I login as the first user and my permisions for PP editor access is enabled. As far as I can recall this problem only appeared when I updated this site to PP 0.19.
I can send you my login credentials so you can take a look. Just tell me the access that you like.
__________________
Sun, 03/05/2009 - 15:07
#5
I will contact you privately
I will contact you privately to agree on credentials.
Mon, 04/05/2009 - 15:23
#6
Here is the diagnosis
Hi,
After logging into your site and looking around, here is my diagnosis:
You have a block EditionsList enabled for the theme tma_custom (but not for tma2) in the content bottom area. This block is configured from a view that uses ajax.
When you are on, for example, node/add/page, the EditionsList block causes the file profiles/prosepoint/modules/views/js/ajax_view.js to be included. There is some sort of problem or clash between this javascript file and the ProsePoint editor, resulting in the editor not working.
I'm not sure whether the bug is with the editor, or with Views (possibly a bit of both), and it's a weird one so I don't have an immediate fix.
For now, I'd suggest the following workaround.
Edit your view such that Use AJAX is set to No. If you don't want to configure this for all the displays of your view, you can override it just for the relevant block.
Alternatively, you can configure the block visibility of the EditionsList block so that it doesn't show up on any node editing or comment editing pages (if you have the editor configured for comments as well), but this may not be practical.
Let me know how you go.
I'll try to get this fixed by the next version of ProsePoint, but I can't make any promises.
Sat, 09/05/2009 - 12:33
#7
PP Editor and View in the same page clash
Beng,
Some updates. At the moment I can use the PP editor, but I have to make all Views invisible in node/add and node/*/edit pages. The PP editor does not function if there is even a single View appearing anywhere in the same page (even if Ajax is disabled).
Andy
__________________
Sat, 09/05/2009 - 17:03
#8
ajax_view.js?
Hi,
Hmm... this would make the bug more severe and urgent than I thought. Tell me, on those pages where the editor doesn't work, does the html include a javascript file named ajax_view.js?
Sat, 09/05/2009 - 18:17
#9
Beng,
I re-checked my Views
Beng,
I re-checked my Views and one of them still had Ajax enabled. I changed this and cleared the cache.
At the moment, it seems the PP editor can co-exist with Views that do not use Ajax. I'll wait for a while before concluding that Ajax is indeed the culprit, but I already made all no-Ajax-Views visible in node/add/* and node/*/edit pages and doing fine with PP editor.
Thanks for giving extra attention to this bug.
__________________
Mon, 11/05/2009 - 12:30
#10
Prospective fix
Hi,
I have a prospective fix. If you'd like to try it on your system, please do the following:
In the file .../profiles/prosepoint/modules/prosepoint/prosepoint_editor/pp_ed.js, change line 141 from:
$(document).ready(Drupal.pp_ed_init);to:
Drupal.pp_ed_init();Remember to turn ajax back on for your views.
This patch will go into the next ProsePoint release, so it is safe to apply it to your system beforehand.
Let me know how you go. Thanks.
Hi,
Hmmm ... the ProsePoint editor should be the same. Nothing was done to it between 0.18 and 0.19. Can you try Clearing the cache to help with common ProsePoint issues and see if that helps?
If it still persists, can you tell me the symptoms, or if you see any error messages, or if your browser reports any javascript errors?
Also, can you post the url of a page that has this issue?