Re: [mezzanine-users] TinyMCE debugging - Mezzanine 4, Django 10, Python 2.7

2017-08-22 Thread Mike Dewhirst 

On 23/08/2017 2:05 AM, Ken Bolton wrote:

Hi Mike,

Spitballing here, have you run the "collectstatic" command?


Ken

Yes I had. But I (re-)discovered the real problem. I checked the nginx 
conf and found that in the past I had switched back to the old (Mezz 3, 
Django 1.8) site because Mezz 4 and Django 1.10 was not showing me any 
content in the Admin.


So I switched forward again, restarted nginx and refreshed the admin 
page to see no content again.


I checked the actual site and saw an Admin link top-left and clicked it. 
Bingo, everything is now working as advertised. I closed the dumb admin 
page and hope to never see it again.


Many thanks for responding. Got me going.

Cheers

Mike




-ken

On Tue, Aug 22, 2017 at 4:20 AM, Mike Dewhirst > wrote:


I'm revisiting a longstanding problem where the TinyMCE editor
doesn't appear and I have edit html by hand.

Not knowing where to start I chose a page in the admin and viewed
source and checked on the existence of all scripts which showed.
On clicking the links, I got some 404 errors but on others the js
appearead. I suspected missing scripts but no - they all appear to
be in place. See "yes" below indicating I have looked in those
dirs. I have stripped out the distracting tags here ...

href="/static/mezzanine/tinymce/tinymce.css"  404 - yes
src="/static/admin/js/core.js" OK - yes
src="/static/admin/js/vendor/jquery/jquery.js" 404 - yes
src="/static/admin/js/jquery.init.js" OK - yes
src="/static/admin/js/admin/RelatedObjectLookups.js" OK - yes
src="/static/admin/js/actions.js" OK - yes
src="/static/admin/js/urlify.js" OK - yes
src="/static/admin/js/prepopulate.js" OK - yes
src="/static/admin/js/vendor/xregexp/xregexp.js" 404 - yes
src="/static/admin/js/calendar.js" OK - yes
src="/static/admin/js/admin/DateTimeShortcuts.js" OK - yes
src="/static/mezzanine/tinymce/tinymce.min.js" 404 - yes
src="/static/mezzanine/tinymce/jquery.tinymce.min.js" 404 - yes
src="/static/mezzanine/js/tinymce_setup.js" OK - yes
src="/static/mezzanine/js/admin/keywords_field.js" OK - yes
src="/static/admin/js/collapse.js" OK - yes


The locations are apparently constructed in settings.py as follows:

# URL prefix for static files.
# Example: "http://media.lawrence.com/static/
"
STATIC_URL = "/static/"

# Absolute path to the directory static files should be collected to.
# Don't put anything in this directory yourself; store your static
files
# in apps' "static/" subdirectories and in STATICFILES_DIRS.
# Example: "/home/media/media.lawrence.com/static/
"
STATIC_ROOT = os.path.join(PROJECT_ROOT, STATIC_URL.strip("/"))

# URL that handles the media served from MEDIA_ROOT. Make sure to
use a
# trailing slash.
# Examples: "http://media.lawrence.com/media/
", "http://example.com/media/;
MEDIA_URL = STATIC_URL + "media/"

# Absolute filesystem path to the directory that will hold
user-uploaded files.
# Example: "/home/media/media.lawrence.com/media/
"
MEDIA_ROOT = os.path.join(PROJECT_ROOT,
*MEDIA_URL.strip("/").split("/"))

I'm not sure about that asterisk.

Any ideas?

Thanks

Mike

-- 
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-users+unsubscr...@googlegroups.com
.
For more options, visit https://groups.google.com/d/optout
.


--
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-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] TinyMCE debugging - Mezzanine 4, Django 10, Python 2.7

2017-08-22 Thread Ken Bolton 
Hi Mike,

Spitballing here, have you run the "collectstatic" command?

-ken

On Tue, Aug 22, 2017 at 4:20 AM, Mike Dewhirst 
wrote:

> I'm revisiting a longstanding problem where the TinyMCE editor doesn't
> appear and I have edit html by hand.
>
> Not knowing where to start I chose a page in the admin and viewed source
> and checked on the existence of all scripts which showed. On clicking the
> links, I got some 404 errors but on others the js appearead. I suspected
> missing scripts but no - they all appear to be in place. See "yes" below
> indicating I have looked in those dirs. I have stripped out the distracting
> tags here ...
>
> href="/static/mezzanine/tinymce/tinymce.css"  404 - yes
> src="/static/admin/js/core.js" OK - yes
> src="/static/admin/js/vendor/jquery/jquery.js" 404 - yes
> src="/static/admin/js/jquery.init.js" OK - yes
> src="/static/admin/js/admin/RelatedObjectLookups.js" OK - yes
> src="/static/admin/js/actions.js" OK - yes
> src="/static/admin/js/urlify.js" OK - yes
> src="/static/admin/js/prepopulate.js" OK - yes
> src="/static/admin/js/vendor/xregexp/xregexp.js" 404 - yes
> src="/static/admin/js/calendar.js" OK - yes
> src="/static/admin/js/admin/DateTimeShortcuts.js" OK - yes
> src="/static/mezzanine/tinymce/tinymce.min.js" 404 - yes
> src="/static/mezzanine/tinymce/jquery.tinymce.min.js" 404 - yes
> src="/static/mezzanine/js/tinymce_setup.js" OK - yes
> src="/static/mezzanine/js/admin/keywords_field.js" OK - yes
> src="/static/admin/js/collapse.js" OK - yes
>
>
> The locations are apparently constructed in settings.py as follows:
>
> # URL prefix for static files.
> # Example: "http://media.lawrence.com/static/;
> STATIC_URL = "/static/"
>
> # Absolute path to the directory static files should be collected to.
> # Don't put anything in this directory yourself; store your static files
> # in apps' "static/" subdirectories and in STATICFILES_DIRS.
> # Example: "/home/media/media.lawrence.com/static/"
> STATIC_ROOT = os.path.join(PROJECT_ROOT, STATIC_URL.strip("/"))
>
> # URL that handles the media served from MEDIA_ROOT. Make sure to use a
> # trailing slash.
> # Examples: "http://media.lawrence.com/media/;, "http://example.com/media/
> "
> MEDIA_URL = STATIC_URL + "media/"
>
> # Absolute filesystem path to the directory that will hold user-uploaded
> files.
> # Example: "/home/media/media.lawrence.com/media/"
> MEDIA_ROOT = os.path.join(PROJECT_ROOT, *MEDIA_URL.strip("/").split("/"))
>
> I'm not sure about that asterisk.
>
> Any ideas?
>
> Thanks
>
> Mike
>
> --
> 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-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Lost in javascript

2017-08-22 Thread Joseph Mohan 
Being rude to a team of devs that spend their free time making these
incredible *FREE* tools to use is ridiculous. You are asking them to give
up their time to answer you so I would suggest being polite and especially
patient.

Take a step back, breathe.

I as well as the others in this thread have done what you are asking with
ease, many times. Mezzanine has a steeper learning curve that Django and
you have already implied in your original post that you don't know much
javascript. So be humble and listen and learn rather than trying to say a
software, written by human beings in their own time and given to you to use
for free is not up to scratch or the docs are lacking (FREEE)

You are welcome to email me privately and I'll try and walk through it.


On Tue, Aug 22, 2017 at 4:17 AM, Ryne Everett  wrote:

> The tone you've taken with other contributors in this thread was out of
> place. To suggest that they are not "knowledgeable" is absurd.
>
> > I didn't 'get' that these
> > changes were to be made in, or added to, the project settings, and not in
> > the various files in the library which I, rightly or wrongly, thought the
> > docs were directing me to.
>
> Patching libraries is not a standard practice and would be unlikely to
> be suggested in software documentation. Frankly, this is a level of
> knowledge our documentation currently assumes.
>
> > If I had seen them in the default settings with
> > blanks or the instruction to 'add or insert here', which is the way
> Django
> > does their models, admin, and views.py, I would not have made this error.
> > So you might suggest that to whoever is on the docs team. Just my 2
> cents.
>
> The docs team is whoever makes pull requests to the docs. I invite you
> to join us.
>
> --
> 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-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.