Thank you for Campsite CMS, guys - your CMS is irreplaceable in a development of a non-profit online magazine, I am involved in now, which also requires a simple writer/editor interface.
After embedding an issuu.com's PDF document widget in a HTML mode of the Campsite's text editor I previewed the article and the Issue widget displayed perfectly.
However, when I attempted to access the editor in ML mode again, I get error message: "Firefox can't find the file at http://MYDOMAINNAME.ORG/javascript/tinymce/themes/advanced/s ource_editor.htm. "
Checking of the server-based files revealed that the mentioned file is there and everything looks OK. My conclusion, therefore, is that my embedding issuu.com <object> partially crashed Campsite's or TinyEditor's/JS.
Can I reset Campsite or/and TinyEd without reinstalling everything?
What Campsite version are you using? I just embeded an issuu document
successfully in 3.4.1 and it was very straight forward by pasting the
embed code in HTML mode.
Cheers,
On Mon, Aug 9, 2010 at 10:26 PM, eworkflow
<campsite-support@lists.sourcefabric.org> wrote:
>
> Thank you for Campsite CMS, guys - your CMS is irreplaceable in a development of a non-profit online magazine, I am involved in now, which also requires a simple writer/editor interface.
>
> After embedding an issuu.com's PDF document widget in a HTML mode of the Campsite's text editor I previewed the article and the Issue widget displayed perfectly.
>
> However, when I attempted to access the editor in ML mode again, I get error message: "Firefox can't find the file at http://MYDOMAINNAME.ORG/javascript/tinymce/themes/advanced/s ource_editor.htm. "
>
> Checking of the server-based files revealed that the mentioned file is there and everything looks OK. My conclusion, therefore, is that my embedding issuu.com <object> partially crashed Campsite's or TinyEditor's/JS.
>
> Can I reset Campsite or/and TinyEd without reinstalling everything?
>
Forgot to mention it displays well in frontend and everything keeps
working ok in backend ;-)
On Mon, Aug 9, 2010 at 10:26 PM, eworkflow
<campsite-support@lists.sourcefabric.org> wrote:
>
> Thank you for Campsite CMS, guys - your CMS is irreplaceable in a development of a non-profit online magazine, I am involved in now, which also requires a simple writer/editor interface.
>
> After embedding an issuu.com's PDF document widget in a HTML mode of the Campsite's text editor I previewed the article and the Issue widget displayed perfectly.
>
> However, when I attempted to access the editor in ML mode again, I get error message: "Firefox can't find the file at http://MYDOMAINNAME.ORG/javascript/tinymce/themes/advanced/s ource_editor.htm. "
>
> Checking of the server-based files revealed that the mentioned file is there and everything looks OK. My conclusion, therefore, is that my embedding issuu.com <object> partially crashed Campsite's or TinyEditor's/JS.
>
> Can I reset Campsite or/and TinyEd without reinstalling everything?
>
I am using 3.3.6 and I definitely "managed" to partially crash editor by regular embedding issue.com widget object into an article. I guess then I just need to upgrade to 3.4. My only concern, at this moment, is that my first project using Campsite is partially developed now (afrobeatjournal.org) and I am not sure whether upgrade to 3.4 is trouble free.
3.4 is backward compatible with 3.3 and includes quite a few bug fixes. I
suggest you make a clone of your site upgrade the clone. If everything works
there then you can safely upgrade on the server.
> I am using 3.3.6 and I definitely "managed" to partially crash editor
> by regular embedding issue.com widget object into an article. I guess then
> I just need to upgrade to 3.4. My only concern, at this moment, is that my
> first project using Campsite is partially developed now (
> afrobeatjournal.org) and I am not sure whether upgrade to 3.4 is trouble
> free.
>
1. Install Campsite on another virtual host (test host)
2. Backup your site from the production host
3. Restore the backup on the test host
4. Upgrade the test host
5. Set the publication alias for the test host in order to be able to test
it
6. Check if the site on the test host shows up properly