[mezzanine-users] MySQL + uWSGI support

[gdx9000]

I see that fabfile.py only supports PostgreSQL and Gunicorn.  Are there any 
plans to support MySQL and uWSGI ? Yes, I know that I can edit 
local_settings file for MySQL.  I also know that I can code the support 
myself but I am looking for any patches, templates etc to use *fabfile.py* 
with MySQL uWSGI.  

(Please resist the urge to give useless responses like: "It's just 
Django",  "Use Django"  etc.  Of course, its just Django.  If I find Django 
documentation clear, without broken links and find it easier, I would have 
already done that)

-- 
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.

[mezzanine-users] Re: Mezzanine fabric deploy support for uwsgi server

[gdx9000]

I am looking for uWSGI deployment support.  I cannot download your diff 
patch.  Can you please post here?

On Wednesday, September 18, 2013 at 1:49:31 PM UTC-4, Rodney Morison wrote:
>
> For the past 2 years I've been using uwsgi over gunicorn, including for my 
> Mezzanine deploys. I finally got around to patching my deploy code into the 
> Mezzanine fabfile. Hopefully, it will find its way into Mezzanine proper: 
> https://bitbucket.org/stephenmcd/mezzanine/pull-request/50/added-support-for-uwsgi-as-alternative-to/diff
>  
>
> I've tested both gunicorn and uwsgi fab create deploy with this code.
>

-- 
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.

[mezzanine-users] Shouldn't comments that are deleted be hidden from other users without permission to that site?

[zruu]

I don't know how it's built, but I noticed something today. When having 
*SESSION_COOKIE_DOMAIN* on for a wildcard solution with all the sites I can 
see others comments that are deleted. I don't think it should be like that.

I would rather hide them from users that do not have permission to that 
specific site. What is Mezzanines standpoint on this matter?

-- 
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] Mezzanine Theme

[Ryne Everett]

Did you put the django wiki's urlpatterns before mezzanine's? A common
pitfall is that mezzanine eats any url pattern so it must be last.

On Mon, Jul 18, 2016 at 3:47 PM, Richard  wrote:

> Hi,
> Thank you for your advice on that. I'm trying to use the Django-Wiki,
> a general wiki app for Django. I was able to configure to use with the
> Mezzanine cms, but i have issues creating a new article.
> " *This slug conflicts with an existing URL.*
>
> This will be the address where your article can be found. Use only
> alphanumeric characters and - or _. Note that you cannot change the slug
> after creating the article."
>
> I'm trying to figure out why there is a conflict even if i provide some
> random name. It's not even picking a single slug. Hopefully i should be
> able to come out with a solution.
>
>
> Thank you,
>
> Richard.
>
>
>
> On Thursday, July 14, 2016 at 8:36:31 AM UTC-5, Eduardo Rivas wrote:
>>
>> It looks like the wiki hasn't been updated since 2014. You will need to
>> find and install the version of Mezzanine that was current at that time
>> (I think Mezzanine 3.1 + Django 1.6). You could try to update it to
>> support later versions of Django and Mezzanine too.
>>
>> Another approach is to look for a wiki solution for Django in general,
>> not Mezzanine specifically. A project like that might be more active.
>>
> --
> 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] Mezzanine Theme

[Richard]

Thank you, I think your second option is what i'm trying to do now. I'm 
trying to integrate the django-wiki with the mezzanine cms. I'm able to 
connect the wiki, but when i try to add new articles in the wiki - i'm 
getting the error 'slug already defined'. I'm trying to fix that now.
Thank you for all the support.



On Thursday, 14 July 2016 08:36:31 UTC-5, Eduardo Rivas wrote:
>
> It looks like the wiki hasn't been updated since 2014. You will need to 
> find and install the version of Mezzanine that was current at that time 
> (I think Mezzanine 3.1 + Django 1.6). You could try to update it to 
> support later versions of Django and Mezzanine too. 
>
> Another approach is to look for a wiki solution for Django in general, 
> not Mezzanine specifically. A project like that might be more active. 
>

-- 
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.

[mezzanine-users] Re: 404 on /accounts/update/

[zruu]

I came across a solution for this:

def user_subdomain(request):
if request.META['HTTP_HOST'] == settings.NETWORK_DOMAIN:
return {
'user': None,
}
else:
username = request.META['HTTP_HOST'].split('.')[0]
sub_user = User.objects.get(username=username)
return {
'user': user,
}


Den måndag 18 juli 2016 kl. 12:55:50 UTC+2 skrev zruu:
>
> For some reason I do not know why, when I write this context processor I 
> can't go to /accounts/update/ anymore. It displays a 404.
>
> def user_subdomain(request):
> from django.shortcuts import get_object_or_404
> username = request.META['HTTP_HOST'].split('.')[0]
> user = get_object_or_404(User, username=username)
> return {
> 'user': user,
> }
>
> Everything else works just fine, and I can get to the login page etc.
>

-- 
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.