[mezzanine-users] Re: Fabric file and related resources for deploying Mezzanine to Webfaction

[Ibn Saeed]

Thanks eduardo

Just signed up via your referral link. Ill test out the 14 day trial period.

Any pointers for new users to webfaction.

On Tuesday, June 10, 2014 9:27:07 AM UTC+4, Eduardo Rivas wrote:
>
> Hello everyone! Since I started with Mezzanine/Django I've been deploying 
> my sites to Webfaction  
> (that's a referral link). Even though their one-click installers are great, 
> they make it hard to keep your Django version up to date and automate the 
> deployment process. For that you need to go beyond the official docs 
> (however, tutorials are not hard to find). I decided to create my own 
> version of the Fabric script that ships with Mezzanine and automate the 
> whole deployment process using the Webfaction API (knowing that Webfaction 
> accounts don't have root access to install stuff). And so, Mezzanine-WebF 
>  was born. I have used it 
> internally for months and others have given it a shot, providing valuable 
> feedback and bug fixes, so I'm confident it's reached an acceptable 
> stability.
>
> So, if you would like to automate deployment of Mezzanine sites to a 
> Webfaction shared hosting account, this is the tool for the job. Feel free 
> to report any bugs you find on Github's issue tracker and contribute fixes 
> if you can. Please note you should be familiar enough with 
> Django/Mezzanine, Fabric, and Webfaction to use the tool, and please read 
> the README. I hope it helps a few. Here's the link again: 
> https://github.com/jerivas/mezzanine-webf.
>

-- 
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: modeltranslations - round 2

[Mathias Ettinger]

Just corrected a few things for the front-end language selector and pushed 
an updated version of cartridge as well.

I tried the TabbedExternalJqueryTranslationAdmin class instead of 
TranslationAdmin and couldn’t get the meta tag area to show. Does it happen 
for you too? Or is there something else to do in order to get it working?

If it is not possible to show extra area like this that are hidden by 
default, we definitely need to write our own custom class on top of 
TranslationAdmin (meaning: core.BaseTranslationModelAdmin). I’m also unsure 
if Translation{Tabular,Stacked}Inline also need to integrates some 
tabbing-awareness code (wether it is a global switch or a per field one). 
But I modified a little bit their admin classes to help integrate it if 
needed.


Le samedi 7 juin 2014 02:26:50 UTC+2, Eduardo Rivas a écrit :
>
> Hey everybody. I've been trying out Mathias master branch and everything 
> is working smoothly. As I said, I'm also exploring ways to enable toggling 
> translation fields in the Admin. Turns out Model Translation (MT) provides 
> two admin classes (docs 
> )
>  
> to include the required static resources for this purpose: 
> TabbedTranslationAdmin 
> and TabbedExternalJqueryTranslationAdmin. The first one seems to fail as 
> it uses Django's jQuery, but the second one works as expected (though it 
> looks kinda ugly in Grappelli) by using external jQuery resources.
>
> I have a couple of questions at this point:
>
>1. Should we use these classes or create our own (considering 
>Mezzanine already includes jQuery and jQuery UI)?
>2. Should we create a toggle for each field (as MT does), or just a 
>"global" toggle to hide/show all fields of a specified language? I favor 
>the second option, as giving each field it's own toggle seems overly messy 
>and confusing for the end user.
>
> Hope to hear from you soon. BTW, if you want to try out MT's default 
> implementation, simply replace all occurrences of TranslationAdmin with 
> TabbedExternalJqueryTranslationAdmin 
> in mezzanine.core.admin.
>

-- 
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] disabling threaded comments

[James Larkin]

Introduction: I'm pretty new Django / Mezzanine (generally I'm more 
involved in designing but I'm trying to get up to speed on everything) 

I'm struggling with a few things so what hell might as well ask

I want to disable comments and the blog.

I've removed the blog from the INSTALLED_APPS settings and this works fine

However the comments seem to be more part of the core of Mezzanine unless 
I'm misunderstanding things?

Could anyone tell me what's the best way to go around removing them?

At the moment I've created a new app for my project I'm working on and into 
admin.py I've put the following

from django.contrib import admin
>
> from mezzanine.generic.models import ThreadedComment
>
> admin.site.unregister(ThreadedComment)
>

This works for what I want and comments are removed from the admin 
interface.

Am I missing something or have I gone about it the completely wrong way? (I 
Googled this to bits as well before posting and struggled to find an answer 
that made sense) 

Thanks in advance 

James

-- 
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] disabling threaded comments

[Josh Cartmell]

Hey James, the comment functionality is baked into Mezzanine (part of
mezzanine.generic), but comments are only present on the blog by default.
As long as you don't add it to anything you create there won't be any
outward facing comments on the site.

Since you've also unregistered them from the admin it looks like you've
accomplished everything you wanted to!

Good work =)


On Tue, Jun 10, 2014 at 9:55 AM, James Larkin 
wrote:

> Introduction: I'm pretty new Django / Mezzanine (generally I'm more
> involved in designing but I'm trying to get up to speed on everything)
>
> I'm struggling with a few things so what hell might as well ask
>
> I want to disable comments and the blog.
>
> I've removed the blog from the INSTALLED_APPS settings and this works fine
>
> However the comments seem to be more part of the core of Mezzanine unless
> I'm misunderstanding things?
>
> Could anyone tell me what's the best way to go around removing them?
>
> At the moment I've created a new app for my project I'm working on and
> into admin.py I've put the following
>
> from django.contrib import admin
>>
>> from mezzanine.generic.models import ThreadedComment
>>
>> admin.site.unregister(ThreadedComment)
>>
>
> This works for what I want and comments are removed from the admin
> interface.
>
> Am I missing something or have I gone about it the completely wrong way?
> (I Googled this to bits as well before posting and struggled to find an
> answer that made sense)
>
> Thanks in advance
>
> James
>
> --
> 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] disabling threaded comments

[James Larkin]

Thanks Josh (want to try and make sure I'm using best practices) also I see 
I have your website open in another tab :) 

It bugs me it's not a simple case of just removing it like with the blog 
app but oh well. I also don't like having things present if they don't need 
to be ( hence a loose comments tab that isn't required in the admin 
interface bugs me )

Now to start hacking flexipages as a starting point for world domination 

On Tuesday, 10 June 2014 16:30:22 UTC+2, Josh Cartmell wrote:
>
> Hey James, the comment functionality is baked into Mezzanine (part of 
> mezzanine.generic), but comments are only present on the blog by default.  
> As long as you don't add it to anything you create there won't be any 
> outward facing comments on the site.
>
> Since you've also unregistered them from the admin it looks like you've 
> accomplished everything you wanted to!
>
> Good work =)
>
>
> On Tue, Jun 10, 2014 at 9:55 AM, James Larkin  > wrote:
>
>> Introduction: I'm pretty new Django / Mezzanine (generally I'm more 
>> involved in designing but I'm trying to get up to speed on everything) 
>>
>> I'm struggling with a few things so what hell might as well ask
>>
>> I want to disable comments and the blog.
>>
>> I've removed the blog from the INSTALLED_APPS settings and this works fine
>>
>> However the comments seem to be more part of the core of Mezzanine unless 
>> I'm misunderstanding things?
>>
>> Could anyone tell me what's the best way to go around removing them?
>>
>> At the moment I've created a new app for my project I'm working on and 
>> into admin.py I've put the following
>>
>> from django.contrib import admin
>>>
>>> from mezzanine.generic.models import ThreadedComment
>>>
>>> admin.site.unregister(ThreadedComment)
>>>
>>
>> This works for what I want and comments are removed from the admin 
>> interface.
>>
>> Am I missing something or have I gone about it the completely wrong way? 
>> (I Googled this to bits as well before posting and struggled to find an 
>> answer that made sense) 
>>
>> Thanks in advance 
>>
>> James
>>
>> -- 
>> 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.
>>
>
>

-- 
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: database error while running migration

[Federico Bruni]

Any pointer?
I don't want to destroy the project and re-deploy from scratch.

Il giorno mercoledì 4 giugno 2014 12:05:17 UTC+2, Federico Bruni ha scritto:
>
> Hi all
>
> I have a problem with the database migration during a deployment.
>
> I have changed only the LANGUAGE_CODE variable in settings.py
> When I launch 'fab deploy' I get this error:
>
> '''
> out: django.db.utils.ProgrammingError: ERROR:  the relation "conf_setting" 
> already exists
> [xx.xx.xx.xx] out: 
> [xx.xx.xx.xx] out: 
>
> Fatal error: run() received nonzero return code 1 while executing!
>
> Requested: /home/fede/.virtualenvs/test/bin/python 
> /home/fede/.virtualenvs/test/project/manage.py migrate --noinput
> Executed: /bin/bash -l -c "cd /home/fede/.virtualenvs/test/project && 
> source /home/fede/.virtualenvs/test/bin/activate && 
> /home/fede/.virtualenvs/test/bin/python 
> /home/fede/.virtualenvs/test/project/manage.py migrate --noinput"
>
> Aborting.
> '''
>
> What should I check?
> Thanks in advance
> Federico
>
>
>

-- 
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: database error while running migration

[Josh Cartmell]

Hey Federico, shot in the dark here, but was South definitely installed
when you deployed in the first place?  I'm wondering if some of the records
of migrations are missing.

I could be totally off and I'm not sure how changing the language code
would affect the db.


On Tue, Jun 10, 2014 at 12:07 PM, Federico Bruni  wrote:

> Any pointer?
> I don't want to destroy the project and re-deploy from scratch.
>
> Il giorno mercoledì 4 giugno 2014 12:05:17 UTC+2, Federico Bruni ha
> scritto:
>
>> Hi all
>>
>> I have a problem with the database migration during a deployment.
>>
>> I have changed only the LANGUAGE_CODE variable in settings.py
>> When I launch 'fab deploy' I get this error:
>>
>> '''
>> out: django.db.utils.ProgrammingError: ERROR:  the relation
>> "conf_setting" already exists
>> [xx.xx.xx.xx] out:
>> [xx.xx.xx.xx] out:
>>
>> Fatal error: run() received nonzero return code 1 while executing!
>>
>> Requested: /home/fede/.virtualenvs/test/bin/python
>> /home/fede/.virtualenvs/test/project/manage.py migrate --noinput
>> Executed: /bin/bash -l -c "cd /home/fede/.virtualenvs/test/project &&
>> source /home/fede/.virtualenvs/test/bin/activate &&
>> /home/fede/.virtualenvs/test/bin/python 
>> /home/fede/.virtualenvs/test/project/manage.py
>> migrate --noinput"
>>
>> Aborting.
>> '''
>>
>> What should I check?
>> Thanks in advance
>> Federico
>>
>>
>>  --
> 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: database error while running migration

[Federico Bruni]

Hey Josh

no, South was not installed. I thought it was a dependency of Mezzanine,
but I see that it's optional:
https://pypi.python.org/pypi/Mezzanine/3.1.5

I've installed it, added it to the requirements and pushed to the
repository, but I'm getting the same error.

I've deployed from scratch. I'll see next time..

Thank you
Federico

2014-06-10 18:19 GMT+02:00 Josh Cartmell :

> Hey Federico, shot in the dark here, but was South definitely installed
> when you deployed in the first place?  I'm wondering if some of the records
> of migrations are missing.
>
> I could be totally off and I'm not sure how changing the language code
> would affect the db.
>
>
> On Tue, Jun 10, 2014 at 12:07 PM, Federico Bruni 
> wrote:
>
>> Any pointer?
>> I don't want to destroy the project and re-deploy from scratch.
>>
>> Il giorno mercoledì 4 giugno 2014 12:05:17 UTC+2, Federico Bruni ha
>> scritto:
>>
>>> Hi all
>>>
>>> I have a problem with the database migration during a deployment.
>>>
>>> I have changed only the LANGUAGE_CODE variable in settings.py
>>> When I launch 'fab deploy' I get this error:
>>>
>>> '''
>>> out: django.db.utils.ProgrammingError: ERROR:  the relation
>>> "conf_setting" already exists
>>> [xx.xx.xx.xx] out:
>>> [xx.xx.xx.xx] out:
>>>
>>> Fatal error: run() received nonzero return code 1 while executing!
>>>
>>> Requested: /home/fede/.virtualenvs/test/bin/python
>>> /home/fede/.virtualenvs/test/project/manage.py migrate --noinput
>>> Executed: /bin/bash -l -c "cd /home/fede/.virtualenvs/test/project &&
>>> source /home/fede/.virtualenvs/test/bin/activate &&
>>> /home/fede/.virtualenvs/test/bin/python 
>>> /home/fede/.virtualenvs/test/project/manage.py
>>> migrate --noinput"
>>>
>>> Aborting.
>>> '''
>>>
>>> What should I check?
>>> Thanks in advance
>>> Federico
>>>
>>>
>>>  --
>> 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 a topic in the
> Google Groups "Mezzanine Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/mezzanine-users/7Hz_5DK_Q0Q/unsubscribe.
> To unsubscribe from this group and all its topics, 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: pg_restore error

[Federico Bruni]

I've just had this same problem and the command above didn't work at first.
It worked when I switched the local to english:

export LANG=C
pg_restore -c -d DATABASE FILE

Maybe it's just a coincidence?



2014-03-27 20:30 GMT+01:00 Federico Bruni :

> I've resolved following the suggestion of Ken in this thread: using the
> commands present in fabfile.py, that is:
>
> pg_dump -Fc DATABASE > FILE
> pg_restore -c -d DATABASE FILE
>
> Though I can't remember exactly what I used before.. probably I didn't use
> the -c  option in pg_restore:
>
> -c, --clean
>Clean (drop) database objects before recreating them. (This
> might
>generate some harmless error messages, if any objects were not
> present
>in the destination database.)
>
>
>
>
> 2014-03-27 18:15 GMT+01:00 Neum Schmickrath :
>
> What are the pg_ commands you are using? These are the commands I use to
>> dump and then restore and I've never had a problem.
>>
>> pg_dump -U USERNAME -F t -f NAMEOF.backup DATABASE-NAME
>>
>> pg_restore -d DATABASE-NAME -O -U USERNAME NAMEOF.backup
>>
>>
>>
>> On Monday, March 24, 2014 2:28:41 AM UTC-6, Federico Bruni wrote:
>>>
>>> I've made the dump of the local database and I've tried to restore it on
>>> the server, but I'm getting the error below.
>>> BTW, how can I force the output to be in english? I've tried LANG=C but
>>> didn't work. Should I change the locale on the server?
>>>
>>> Any help appreciated.
>>>
>>> _restore: [archiviatore (db)] Errore nella voce TOC 2142; 2606 26962 FK
>>> CONSTRAINT to_blogpost_id_refs_id_6404941b fede
>>> pg_restore: [archiviatore (db)] could not execute query: ERRORE:  il
>>> vincolo "to_blogpost_id_refs_id_6404941b" per la relazione
>>> "blog_blogpost_related_posts" esiste già
>>> Command was: ALTER TABLE ONLY blog_blogpost_related_posts
>>> ADD CONSTRAINT to_blogpost_id_refs_id_6404941b FOREIGN KEY
>>> (to_blogpost_id)...
>>> pg_restore: [archiviatore (db)] Errore nella voce TOC 2172; 2606 26967
>>> FK CONSTRAINT twitter_tweet_query_id_fkey fede
>>> pg_restore: [archiviatore (db)] could not execute query: ERRORE:  il
>>> vincolo "twitter_tweet_query_id_fkey" per la relazione "twitter_tweet"
>>> esiste già
>>> Command was: ALTER TABLE ONLY twitter_tweet
>>> ADD CONSTRAINT twitter_tweet_query_id_fkey FOREIGN KEY (query_id)
>>> REFERENCES twitter_quer...
>>> pg_restore: [archiviatore (db)] Errore nella voce TOC 2133; 2606 26972
>>> FK CONSTRAINT user_id_refs_id_40c41112 fede
>>> pg_restore: [archiviatore (db)] could not execute query: ERRORE:  il
>>> vincolo "user_id_refs_id_40c41112" per la relazione "auth_user_groups"
>>> esiste già
>>> Command was: ALTER TABLE ONLY auth_user_groups
>>> ADD CONSTRAINT user_id_refs_id_40c41112 FOREIGN KEY (user_id)
>>> REFERENCES auth_user(id)...
>>> pg_restore: [archiviatore (db)] Errore nella voce TOC 2135; 2606 26977
>>> FK CONSTRAINT user_id_refs_id_4dc23c39 fede
>>> pg_restore: [archiviatore (db)] could not execute query: ERRORE:  il
>>> vincolo "user_id_refs_id_4dc23c39" per la relazione
>>> "auth_user_user_permissions" esiste già
>>> Command was: ALTER TABLE ONLY auth_user_user_permissions
>>> ADD CONSTRAINT user_id_refs_id_4dc23c39 FOREIGN KEY (user_id)
>>> REFERENCES aut...
>>> ATTENZIONE: errore ignorato durante il ripristino: 219
>>>
>>  --
>> 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/otAYtS2qLuE/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, 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.

[mezzanine-users] Re: Mezzanine-Cartridge Problem when view product image

[green]

Hi Ken,
Thank you.  That helps a lot.  It is now working perfectly. 
Kind regards,
Jane

On Monday, 9 June 2014 13:55:02 UTC+1, green wrote:
>
> Not sure what went wrong and where to start.  I have 
> Cartridge==0.9.3
> Django==1.6.4
> Mezzanine==3.1.4
>
> Problem:  When click on product image in a full site, I do not get a 
> floating/overlay image window as seen in the Mezzanine demo site. Instead, 
> I get the display image, see attached, added on top of the current view 
> pushing down all other content. 
>
>
> 
> Any suggestion on where I should start looking would be much appreciated.
>
> Thank you in advance.
>

-- 
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: Saw that I should post my site here.

[James Larkin]

While the functionality may be there the visuals are really letting it down 
I'm sorry to say.

The contrast / colours / background images / legibility make it extremely 
painful to use :( 

I'd try to get the opinions of a few friends on it and work out some colour 
schemes that you like.

James

On Friday, 6 June 2014 06:16:46 UTC+2, nathan wrote:
>
> My site(s) are mezzanine/django sites.  The one that is pretty well 
> polished is http://www.brokensoundbooking.com .  I am making some changes 
> that I think will be fantastic including a thumbnailable band photo for 
> navigation menus.  It is in my new "Band" page which inherits from the 
> regular mezzanine page model.
> -Nate
> Thanks Stephen, Josh and all the great contributers.
>

-- 
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] can't upload img into media library with new firefox

[roland balint]

just grabbed a fresh firefox and the media library fails to show the 
"select file" button in it, IE8 OK ...



thx
rb

-- 
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] disabling threaded comments

[Danny]

On 11/06/2014 12:32 AM, James Larkin wrote:

Thanks Josh (want to try and make sure I'm using best practices) also I
see I have your website open in another tab :)

It bugs me it's not a simple case of just removing it like with the blog
app but oh well. I also don't like having things present if they don't
need to be ( hence a loose comments tab that isn't required in the admin
interface bugs me )


I didn't want comments on my site either and the easiest thing to do was
to just comment out/remove those sections from the relevant templates.




Now to start hacking flexipages as a starting point for world domination

On Tuesday, 10 June 2014 16:30:22 UTC+2, Josh Cartmell wrote:

Hey James, the comment functionality is baked into Mezzanine (part
of mezzanine.generic), but comments are only present on the blog by
default.  As long as you don't add it to anything you create there
won't be any outward facing comments on the site.

Since you've also unregistered them from the admin it looks like
you've accomplished everything you wanted to!

Good work =)


On Tue, Jun 10, 2014 at 9:55 AM, James Larkin > wrote:

Introduction: I'm pretty new Django / Mezzanine (generally I'm
more involved in designing but I'm trying to get up to speed on
everything)

I'm struggling with a few things so what hell might as well ask

I want to disable comments and the blog.

I've removed the blog from the INSTALLED_APPS settings and this
works fine

However the comments seem to be more part of the core of
Mezzanine unless I'm misunderstanding things?

Could anyone tell me what's the best way to go around removing them?

At the moment I've created a new app for my project I'm working
on and into admin.py I've put the following

from django.contrib import admin

from mezzanine.generic.models import ThreadedComment

admin.site.unregister(ThreadedComment)


This works for what I want and comments are removed from the
admin interface.

Am I missing something or have I gone about it the completely
wrong way? (I Googled this to bits as well before posting and
struggled to find an answer that made sense)

Thanks in advance

James

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


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




--
Email: molo...@gmail.com

--
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] disabling threaded comments

[James Larkin]

Hi Danny,

My problem with just removing from templates ... it's just visually not 
available but the code possibly still exists to process the comments or am 
I wrong? 

I could have tweaked things with a display:none bit of css to just remove 
it visually from the admin menu but I'm still not happy with that.

James

On Tuesday, 10 June 2014 23:30:11 UTC+2, Danny S wrote:
>
> On 11/06/2014 12:32 AM, James Larkin wrote: 
> > Thanks Josh (want to try and make sure I'm using best practices) also I 
> > see I have your website open in another tab :) 
> > 
> > It bugs me it's not a simple case of just removing it like with the blog 
> > app but oh well. I also don't like having things present if they don't 
> > need to be ( hence a loose comments tab that isn't required in the admin 
> > interface bugs me ) 
>
> I didn't want comments on my site either and the easiest thing to do was 
> to just comment out/remove those sections from the relevant templates. 
>
>
> > 
> > Now to start hacking flexipages as a starting point for world domination 
> > 
> > On Tuesday, 10 June 2014 16:30:22 UTC+2, Josh Cartmell wrote: 
> > 
> > Hey James, the comment functionality is baked into Mezzanine (part 
> > of mezzanine.generic), but comments are only present on the blog by 
> > default.  As long as you don't add it to anything you create there 
> > won't be any outward facing comments on the site. 
> > 
> > Since you've also unregistered them from the admin it looks like 
> > you've accomplished everything you wanted to! 
> > 
> > Good work =) 
> > 
> > 
> > On Tue, Jun 10, 2014 at 9:55 AM, James Larkin  > > wrote: 
> > 
> > Introduction: I'm pretty new Django / Mezzanine (generally I'm 
> > more involved in designing but I'm trying to get up to speed on 
> > everything) 
> > 
> > I'm struggling with a few things so what hell might as well ask 
> > 
> > I want to disable comments and the blog. 
> > 
> > I've removed the blog from the INSTALLED_APPS settings and this 
> > works fine 
> > 
> > However the comments seem to be more part of the core of 
> > Mezzanine unless I'm misunderstanding things? 
> > 
> > Could anyone tell me what's the best way to go around removing 
> them? 
> > 
> > At the moment I've created a new app for my project I'm working 
> > on and into admin.py I've put the following 
> > 
> > from django.contrib import admin 
> > 
> > from mezzanine.generic.models import ThreadedComment 
> > 
> > admin.site.unregister(ThreadedComment) 
> > 
> > 
> > This works for what I want and comments are removed from the 
> > admin interface. 
> > 
> > Am I missing something or have I gone about it the completely 
> > wrong way? (I Googled this to bits as well before posting and 
> > struggled to find an answer that made sense) 
> > 
> > Thanks in advance 
> > 
> > James 
> > 
> > -- 
> > 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 
> > . 
> > 
> > 
> > -- 
> > 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. 
>
>
>
> -- 
> Email: mol...@gmail.com  
>

-- 
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] can't upload img into media library with new firefox

[Stephen McDonald]

You probably need to install the Flash plugin.

There's an open issue for replacing this with something that doesn't need
Flash, feel free to pitch in.


On Wed, Jun 11, 2014 at 6:14 AM, roland balint  wrote:

> just grabbed a fresh firefox and the media library fails to show the
> "select file" button in it, IE8 OK ...
>
>
> 
>
> thx
> rb
>
> --
> 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.
>



-- 
Stephen McDonald
http://jupo.org

-- 
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: Fabric file and related resources for deploying Mezzanine to Webfaction

[Eduardo Rivas]

Thanks for the interest guys. Ibn, I recommend you take a look at the 
Webfaction docs and read the fabfile to have an idea of what it does. Some 
knowledge of Postgres and Git will also be useful. Finally, when you 
deploy, keep in mind many settings have default values in fabsettings.py, 
so just comment out any particular setting to use the default. This will 
maintain the settings you actually need to touch to a minimum.

-- 
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] disabling threaded comments

[Danny]

No, James, you're right. Removing comments from the templates doesn't hide
the admin side of things, just the user-visible side.


On 11 June 2014 07:23, James Larkin  wrote:

> Hi Danny,
>
> My problem with just removing from templates ... it's just visually not
> available but the code possibly still exists to process the comments or am
> I wrong?
>
> I could have tweaked things with a display:none bit of css to just remove
> it visually from the admin menu but I'm still not happy with that.
>
> James
>
>
> On Tuesday, 10 June 2014 23:30:11 UTC+2, Danny S wrote:
>
>> On 11/06/2014 12:32 AM, James Larkin wrote:
>> > Thanks Josh (want to try and make sure I'm using best practices) also I
>> > see I have your website open in another tab :)
>> >
>> > It bugs me it's not a simple case of just removing it like with the
>> blog
>> > app but oh well. I also don't like having things present if they don't
>> > need to be ( hence a loose comments tab that isn't required in the
>> admin
>> > interface bugs me )
>>
>> I didn't want comments on my site either and the easiest thing to do was
>> to just comment out/remove those sections from the relevant templates.
>>
>>
>> >
>> > Now to start hacking flexipages as a starting point for world
>> domination
>> >
>> > On Tuesday, 10 June 2014 16:30:22 UTC+2, Josh Cartmell wrote:
>> >
>> > Hey James, the comment functionality is baked into Mezzanine (part
>> > of mezzanine.generic), but comments are only present on the blog by
>> > default.  As long as you don't add it to anything you create there
>> > won't be any outward facing comments on the site.
>> >
>> > Since you've also unregistered them from the admin it looks like
>> > you've accomplished everything you wanted to!
>> >
>> > Good work =)
>> >
>> >
>> > On Tue, Jun 10, 2014 at 9:55 AM, James Larkin > > > wrote:
>> >
>> > Introduction: I'm pretty new Django / Mezzanine (generally I'm
>> > more involved in designing but I'm trying to get up to speed on
>> > everything)
>> >
>> > I'm struggling with a few things so what hell might as well ask
>> >
>> > I want to disable comments and the blog.
>> >
>> > I've removed the blog from the INSTALLED_APPS settings and this
>> > works fine
>> >
>> > However the comments seem to be more part of the core of
>> > Mezzanine unless I'm misunderstanding things?
>> >
>> > Could anyone tell me what's the best way to go around removing
>> them?
>> >
>> > At the moment I've created a new app for my project I'm working
>> > on and into admin.py I've put the following
>> >
>> > from django.contrib import admin
>> >
>> > from mezzanine.generic.models import ThreadedComment
>> >
>> > admin.site.unregister(ThreadedComment)
>> >
>> >
>> > This works for what I want and comments are removed from the
>> > admin interface.
>> >
>> > Am I missing something or have I gone about it the completely
>> > wrong way? (I Googled this to bits as well before posting and
>> > struggled to find an answer that made sense)
>> >
>> > Thanks in advance
>> >
>> > James
>> >
>> > --
>> > 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
>> > .
>> >
>> >
>> > --
>> > 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.
>>
>>
>>
>> --
>> Email: mol...@gmail.com
>>
>


-- 
molo...@gmail.com

-- 
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] Newbie questions regarding Drum - tags and skinning

[Duke Dougal]

I'm a total newbie to Django, Mezzanine and Drum, but have some experience 
with Python.

I do like Drum but would need tags or keywords. I'm happy to poke around 
and try to add this functionality in, but if someone can recommend an 
overall approach that would mean I could implement it much faster.

Also, if someone could point me in the right direction for skinning Drum 
that would also be much appreciated.  Is there a "well known approach" for 
skinning Drum or do I just have to hack on the CSS?

Any assistance pointing me in the right direction would be much appreciated.


-- 
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: Proposal: can_move permission (was: page_move signals)

[Stephen McDonald]

On Sun, Jun 8, 2014 at 8:18 AM, Ahmad Khayyat  wrote:

> There is one issue with the current approach. The exception message is
> shown using Django messages, which displays the message at the top of the
> page. If the page tree is scrolled down, the user will see that the illegal
> move move was reverted, but will not see the message, which is unsettling!
>
> Perhaps we should scroll to the top when the message is displayed? Any
> better solutions? or is it not big of an issue?
>

Unless I'm missing something from when I tested it, this isn't an issue -
since you call location.reload() on error the user should always be put
back to the top of the screen, where they'll see the message.


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



-- 
Stephen McDonald
http://jupo.org

-- 
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: Proposal: can_move permission (was: page_move signals)

[Ahmad Khayyat]

This behavior is browser-dependent, apparently. I ran into this issue on
chromium, where a page reload gets you back to the same position in the
page as before the reload. In firefox, a reload puts you back at the top of
the page.

-- 
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: Proposal: can_move permission (was: page_move signals)

[Stephen McDonald]

That makes sense - maybe we could add some scroll to top code then.


On Wed, Jun 11, 2014 at 12:26 PM, Ahmad Khayyat  wrote:

> This behavior is browser-dependent, apparently. I ran into this issue on
> chromium, where a page reload gets you back to the same position in the
> page as before the reload. In firefox, a reload puts you back at the top of
> the page.
>
> --
> 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.
>



-- 
Stephen McDonald
http://jupo.org

-- 
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: Fabric file and related resources for deploying Mezzanine to Webfaction

[Ibn Saeed]

I have knowledge of postgres and git.  Just wanted to know about Webfaction.

Here is what i found out, on thier support site. Someone had asked about
installing mezzanine cms on webfaction and someone from the webfaction team
answered.

https://community.webfaction.com/questions/10290/how-can-i-install-the-mezzanine-cms-for-django-on-webfaction




On Wed, Jun 11, 2014 at 2:57 AM, Eduardo Rivas 
wrote:

> Thanks for the interest guys. Ibn, I recommend you take a look at the
> Webfaction docs and read the fabfile to have an idea of what it does. Some
> knowledge of Postgres and Git will also be useful. Finally, when you
> deploy, keep in mind many settings have default values in fabsettings.py,
> so just comment out any particular setting to use the default. This will
> maintain the settings you actually need to touch to a minimum.
>
> --
> 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/KrU1t4Lf_fk/unsubscribe.
> To unsubscribe from this group and all its topics, 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.