This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.
Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.
Before posting questions here you might want to review the developer documentation.
Hi,
I've upgraded my site to the latest version and the FCK Editor controls stopped rendering on the page. My custom skin is based on one of the skins from the version 2.2.9 or similar . Would hat be a culprit? The CKEditor works fine but it is missing a critical feature when adding an image to the blog - it does not have the option to search for an image on the server.
Anyone has seen this issue recently?
Are you getting any script errors?
Are you sure it is skin related? ie changing skins makes it work?
No errors - just the controls on the top of the editor are not rendering at all: I have empty line with a word "Source" and underneath it empty line with a word "Style". The behavior is the same for my custom skin or built in skins.
During the upgrade I've all the existing files and uploaded 2.3.3.0 to an empty root directory
Are you using a custom javascript config file for the editor to customize the toolbars or are you using a custom version of mojoEditor.config to control the list of editors?
No. Everything is out of the box.
Did you try to keep your old web.config?
If all else fails I would tryuploading the /ClientScript folder in case there were transfer errors.
I would also clear the browser cache and or try other browsers.
Hope it helps,
Joe
It was some kind of permission issue. I was aliasing (ie parked my domain on another hosted site) a site on NoDaddy. Once I moved the domain onto its own dedicated hosting the issue went away.