Re: [mezzanine-users] 500 internal server error

2017-06-03 Thread Melvyn Sopacua
On Saturday 03 June 2017 18:19:37 Marcello Console wrote: > Hi, thank you for your support Melvyn . > As far as syntax error: i run python manage.py check and it says it's > ok. As for debug: it was set to True > As far as for mail_admins: from the shell i got an error, but it was > becouse google

Re: [mezzanine-users] 500 internal server error

2017-06-03 Thread Marcello Console
Hi, thank you for your support Melvyn . As far as syntax error: i run python manage.py check and it says it's ok. As for debug: it was set to True As far as for mail_admins: from the shell i got an error, but it was becouse google blocked it. I solved it on google panel and then try successsfully

Re: [mezzanine-users] Simplifying rich text

2017-06-03 Thread Melvyn Sopacua
On Saturday 03 June 2017 09:51:12 Ryne Everett wrote: > > 2) Implement the approach to RichTextField and global editor > > configuration from django- ckeditor, but leave TinyMCE as default. > > Introducing as little incompatibilities as possible would be the > > hard part. > > Sounds like #2 is

Re: [mezzanine-users] Simplifying rich text

2017-06-03 Thread Melvyn Sopacua
On Saturday 03 June 2017 07:40:55 Ken Bolton wrote: > Check out https://github.com/stephenmcd/mezzanine/issues/588 for the > reason. > > TL;DR: Write it as an app, e.g. `mezzanine-ckeditor`; share it with > us. My main concern is not with the editor of choice, but with the RichTextField and

Re: [mezzanine-users] Simplifying rich text

2017-06-03 Thread Ryne Everett
> 2) Implement the approach to RichTextField and global editor configuration > from django- > ckeditor, but leave TinyMCE as default. Introducing as little > incompatibilities as possible > would be the hard part. Sounds like #2 is the approach for improving the core project, though creating a

Re: [mezzanine-users] Simplifying rich text

2017-06-03 Thread Ken Bolton
Hi Melvyn, Check out https://github.com/stephenmcd/mezzanine/issues/588 for the reason. TL;DR: Write it as an app, e.g. `mezzanine-ckeditor`; share it with us. -ken -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this

Re: [mezzanine-users] 500 internal server error

2017-06-03 Thread Melvyn Sopacua
On Saturday 03 June 2017 01:14:57 marco coso wrote: > i had a blog with with mezzanine, it was working, then i installed > mezzanine-api and follow the instructions fort existing project. But > now i always got a 500 internal server error using the browser, and > nothing en error.log (in

Re: [mezzanine-users] Simplifying rich text

2017-06-03 Thread Melvyn Sopacua
On Friday 02 June 2017 20:03:20 Ryne Everett wrote: > The direction this discussion goes hinges on whether ckeditor is a > preferable editor to tinymce or if django-ckeditor just has a more > powerful RichTextField implementation than Mezzanine. Yes, that is why I said, if we take the approach

[mezzanine-users] 500 internal server error

2017-06-03 Thread marco coso
hello i had a blog with with mezzanine, it was working, then i installed mezzanine-api and follow the instructions fort existing project. But now i always got a 500 internal server error using the browser, and nothing en error.log (in access.log i can see the request). So i created a new