Hi Tomaz and John-Gordon,
You are clearly having the same problem, as is someone over on the epEditor blog: http://www.electricputty.co.uk/epeditor/?p=65
The fact that these values are empty
var ep_image_action_id = "";
var ep_link_action_id = "";
var cp_path = "";
means that for some reason when you installed the extension the settings did not getting stored and so the editor doesn’t know where it is. I can’t replicate this problem here so to try and diagnose it I wonder if you can tell me:
Sorry for the problems you are having, I’m sure we’ll get to the bottom of it.
Best wishes,
Malcolm
Hey Malcolm,
I’m having the same problem as the other guys. Namely, my values are empty. I changed the extension settings to point to my scripts folder (which is /js/), but that’s the only change I made. I’ve attached a zip file containing the details from the source code you asked for, because the filters on the forum won’t let me post the parameters from the open body tag.
To answer your questions:
Hope that helps crack the problem. I’d sure love to use this extension! 😊
Hello,
This extension seems pretty good but having a few problems.
When you click on the image or link icon, is it supposed to open up in a chromeless window? for me it opens in a new window but it has scroll bars and stuff….is there supposed to be no scrollbars?
Also, when you past code in the code when you switch over to the html view seems sloppy, like alot of divs or span were added. Any advice on getting it to work cleanly?
Thanks!
Version 1.0.5(beta) now available!
OK, we’ve been back to the drawing board and come at this from a different angle. The problem that everyone seems to be having is that the method we were using to determine the include path from the image manager to the core.system was not robust. It worked for some but not to others and we couldn’t figure out why.
As we were using a module file to process the image uploads anyway we have decided to extend this and use the module directory as the place to store all the editor files. This way the path from there to the core will be the same for everyone and (hopefully) the image manager should work.
Unlike previous version of the epEditor you will need to install both the extension and the module. The extension is used to hook into the CP and render the editor in the publish page, the module is used to create the required records in the exp_actions table and to configure the editor.
Apart from the changes to the installation process the other major update with this release is the ability to manage custom classes via the module interface, so there should be no need to go anywhere near the JavaScript files.
Please give this one a try; there are installation and updating instructions in the read me file. I have run a load of tests here are the only problem I encountered was when I updated from a previous version while I was already logged in to the CP and viewing an publish screen, so please log out before you update the files.
Hi Malcolm,
Just as a quick note to say thanks this version has cleared up all the problems I was having previously. Working fine in my localhost setup so no doubt I shouldn’t have a problem on a live site.
The only thing I couldn’t get to work was resizing images in the editor from within Safari although this does work fine in Firefox so not much of a problem really. I’m guessing this is probably more something to do with Safari than your module though.
So basically thanks for the new version as it seems to be working fine. Great work! 😊
Best wishes,
Mark
A couple of minor fixes from yesterday’s release.
Please download version 1.0.5 from here.
Thanks, Malcolm
A couple of minor fixes from yesterday’s release. Please download version 1.0.5 from here. Thanks, Malcolm
What’s changed in this version Malcolm?
What’s changed in this version Malcolm?
Some minor CSS fixes for the CP screens and a database update. The earlier version only allowed up to 100 chars for the CSS definitions; this has been changed to a text field to give maximum flexibility.
If you have already installed the earlier version you’ll need to upload the new files and then de-install and re-install the module.
In this new version, nothing is showing up!? Maybe because I cannot change the settings?
Hi there,
Can you be a bit more specific about exactly what the problem is? Where is nothing showing up? In the publish screen?
Have you installed the module and extension? Can you view the module and access its settings screens? Have you created a custom field set which uses the epEditor type? Are you editing a weblog entry which uses this field set?
Thanks
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.