Cannot edit content on Rich Text Page

[Ilya Yakunin]

Hi all,

I've just started a new mezzanine project using:
* Mezzanine 4.0.1
* Django 1.8.5
* Python 2.7.10
* SQLite 3.8.10.2
* Linux 3.16.0-4-amd64

with default config. Simply ran mezzanine-project, created a database and ran developement server.

When I try to create a new Rich Text Page within admin interface I get no field for editing my content, it's just a gray div next to the "Content:" field. Server log gives several 404 errors linked with TinyMCE plugins:

[15/Oct/2015 14:57:08] "GET /static/mezzanine/tinymce/themes/advanced/theme.min.js HTTP/1.1" 404 1751
[15/Oct/2015 14:57:08] "GET /static/mezzanine/tinymce/plugins/advimage/plugin.min.js HTTP/1.1" 404 1757
[15/Oct/2015 14:57:08] "GET /static/mezzanine/tinymce/plugins/inlinepopups/plugin.min.js HTTP/1.1" 404 1769
[15/Oct/2015 14:57:08] "GET /static/mezzanine/tinymce/plugins/advlink/plugin.min.js HTTP/1.1" 404 1754

My 'pip freeze' result:
beautifulsoup4==4.4.0
bleach==1.4.1
chardet==2.3.0
Django==1.8.5
django-contrib-comments==1.6.1
django-modeltranslation==0.10.1
filebrowser-safe==0.4.0
future==0.15.0
grappelli-safe==0.4.0
html5lib==0.999999
Mezzanine==4.0.1
oauthlib==1.0.1
Pillow==2.9.0
pytz==2015.4
requests==2.7.0
requests-oauthlib==0.5.0
six==1.9.0
tzlocal==1.2

I tried to collect static files using manage.py, but this doesn't return me lost plugins.

Please, help me to figure out whats going on, any help would be appreciated.

Cheers,
Ilya

[Ryne Everett]

If you're using firefox you may need to go to 127.0.0.1 rather than localhost.

--
You received this message because you are subscribed to the Google Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Eduardo Rivas]

Were you running a Mezzanine 3 site before? I have experienced a problem
where the old tinymce files are cached by the browser. A cache reload
(Ctrl + F5) does the trick.

[Ilya Yakunin]

Yes, I have another Mezzanine 3 project working under Apache virtual
host. Everything works well in that case.

The problem occurs only with new Mezzanine 4 project running under
its own virtualenv. Cache reloading didn't help

> --
> You received this message because you are subscribed to a topic in the

> Google Groups "Mezzanine Users" group.

> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/mezzanine-users/qkFaUzZ8kvQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to

> mezzanine-use...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
Удачи,
Илья

[Eyjolfur Kristjánsson]

Hi.

 

I know this is an old thread, but I am running into exactly the same problem it seems. I.e. getting 404 on those plugin js files. Seems that collect static is not collecting them. I am running Mezzanine 4.2.3, the latest version I believe. 

So if anyone has found an solution for this, I would greatly appreciate if it could be posted here. 

Cheers,

Eyjolfur

[Ken Bolton]

'python manage.py collectstatic` will put the files in your `settings.STATIC_ROOT`. Make sure that directory is being served by your web server. If you are using the fabfile to create and deploy your project, that will happen automatically.

[Eyjolfur Kristjánsson]

Thanks for your quick replay Kenneth.  

I just figured out what was wrong. The problem was not with the collect static per se, other static files for mezzanine and tinymce were collected correctly. The problem was that I am moving a site between servers and using the oppertuninty to upgrade it from Mezzanine 3.0.9 to the newest versions, and had forgotten that I had created to a custom config for the tinymce edit, and it seems to have messed up the process when the editor was loading. Now I will have to look at that config and find out what causes this (and what I wanted to customize in the editor)

Eyjolfur