[mezzanine-users] Re: Introducing Mezzanine's Core Development Team

[automotiveace]

Great stuff and congrats to the team!

On Monday, May 11, 2015 at 5:20:44 PM UTC-4, Stephen McDonald wrote:
>
> Hi all,
>
> Today I'm thrilled to announce the introduction of a core development team 
> for Mezzanine. I've written a detailed post about it, please heave a read:
>
>
> http://blog.jupo.org/2015/05/11/introducing-mezzanines-core-development-team/
>
> TLDR: The new team consists of myself, Josh Cartmell, Ken Bolton, Alex 
> Hill, Ed Rivas, Mathias Ettinger, who have each made huge contributions to 
> the project over several years.
>
> Please join me in welcoming them!
>
>
> -- 
> 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] The Orderable "move" buttons

[Danny]

On 15 May 2015 at 09:49, Stephen McDonald  wrote:

>
>
>
> That is a problem - the admin support is only designed for inlines.
>
> I think there was a thread on here just the other day about a third party
> lib for top-level ordering.
>

Think I found it, Eduardo mentioned django-admin-sortable.

https://github.com/iambrandontaylor/django-admin-sortable

I'll have a look how that one works.

Seeya. Danny.

-- 
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] The Orderable "move" buttons

[Stephen McDonald]

On Fri, May 15, 2015 at 10:17 AM, Danny  wrote:

>
>
> On 15 May 2015 at 09:21, Stephen McDonald  wrote:
>
>>
>>
>> On Fri, May 15, 2015 at 7:45 AM, Danny  wrote:
>>
>>> Hi all,
>>>
>>> I'm doing a new development using Mezzanine master and Django 1.8.1, and
>>> I've got a model that derives from Orderable,
>>> with appropriate admin stuff set up for it too.
>>>
>>> In Mezzanine 3.1.10, the "_order" field was just an integer, so it was
>>> easy to edit, but with the latest mezzanine, it's now been replaced with
>>> the wonderful drag-and-drop arrows. Except, for my new model, they don't
>>> drag and drop!
>>>
>>
>> These have always been drag/drop - the previous behaviour you've seen was
>> a bug. Likely candidate is JavaScript not being hosted correctly. Anyway
>> you're now seeing what should have always worked :-)
>>
>
> Yeah, I realised that - but the bug earlier made it easy to modify the
> order :D
>
>
>>
>>
>>>
>>> Is there something I'm missing with respect to admin setup, or
>>> templates/css/js that I need to add so that the new model has the same
>>> drag/drop functionality as e.g. pages or the inlines for form fields?
>>>
>>
>> Take a look at the models and admin classes in mezzanine.forms that makes
>> full use of this, particularly the admin class for your inlines:
>> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/forms/admin.py#L38
>>
>
>
> I think the problem I'm facing is that the Orderable object is a top-level
> model, not something that's inlined within another model -
>

That is a problem - the admin support is only designed for inlines.

I think there was a thread on here just the other day about a third party
lib for top-level ordering.



> so it doesn't need the "Add another" part that the Tabular/Stacked Inline
> Admin templates provide, nor do I need to do the re-ordering within another
> model.
>
> It's probably more akin to Pages, but without the need for the nested
> hierarchy. I've a feeling I may need to create a new template/javascript
> that behaves like the inline ordering js, but works on items that are not
> inlines. I'll do some more investigation.
>
> Seeya. Danny.
>
>
>>
>>>
>>> I did have a look at, e.g.
>>> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/static/mezzanine/js/admin/dynamic_inline.js#L43
>>> but am not sure if there's something subtle I'm missing that I need to do
>>> to make it work.
>>> Is it possible I need to install grapelli_safe from github master as
>>> well? (I haven't done that yet, just using what's on PyPi)
>>>
>>> Thanks,
>>>
>>> Seeya. Danny.
>>>
>>> --
>>> 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.
>>
>
>
>
> --
> *Danny Sag*
> Chairperson
> Round World Events SA, Inc
> City of Small Gods Terry Pratchett Fan Club -
> http://cityofsmallgods.org.au
>
> *Nullus Anxietas VI - The Australian Discworld Convention* -
> http://ausdwcon.org
> "The Discworld Grand Tour" - Adelaide SA, August 4-6, 2017
>
>
>
>
>
>  --
> 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] The Orderable "move" buttons

[Danny]

On 15 May 2015 at 09:21, Stephen McDonald  wrote:

>
>
> On Fri, May 15, 2015 at 7:45 AM, Danny  wrote:
>
>> Hi all,
>>
>> I'm doing a new development using Mezzanine master and Django 1.8.1, and
>> I've got a model that derives from Orderable,
>> with appropriate admin stuff set up for it too.
>>
>> In Mezzanine 3.1.10, the "_order" field was just an integer, so it was
>> easy to edit, but with the latest mezzanine, it's now been replaced with
>> the wonderful drag-and-drop arrows. Except, for my new model, they don't
>> drag and drop!
>>
>
> These have always been drag/drop - the previous behaviour you've seen was
> a bug. Likely candidate is JavaScript not being hosted correctly. Anyway
> you're now seeing what should have always worked :-)
>

Yeah, I realised that - but the bug earlier made it easy to modify the
order :D


>
>
>>
>> Is there something I'm missing with respect to admin setup, or
>> templates/css/js that I need to add so that the new model has the same
>> drag/drop functionality as e.g. pages or the inlines for form fields?
>>
>
> Take a look at the models and admin classes in mezzanine.forms that makes
> full use of this, particularly the admin class for your inlines:
> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/forms/admin.py#L38
>


I think the problem I'm facing is that the Orderable object is a top-level
model, not something that's inlined within another model - so it doesn't
need the "Add another" part that the Tabular/Stacked Inline Admin templates
provide, nor do I need to do the re-ordering within another model.

It's probably more akin to Pages, but without the need for the nested
hierarchy. I've a feeling I may need to create a new template/javascript
that behaves like the inline ordering js, but works on items that are not
inlines. I'll do some more investigation.

Seeya. Danny.


>
>>
>> I did have a look at, e.g.
>> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/static/mezzanine/js/admin/dynamic_inline.js#L43
>> but am not sure if there's something subtle I'm missing that I need to do
>> to make it work.
>> Is it possible I need to install grapelli_safe from github master as
>> well? (I haven't done that yet, just using what's on PyPi)
>>
>> Thanks,
>>
>> Seeya. Danny.
>>
>> --
>> 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.
>



-- 
*Danny Sag*
Chairperson
Round World Events SA, Inc
City of Small Gods Terry Pratchett Fan Club - http://cityofsmallgods.org.au

*Nullus Anxietas VI - The Australian Discworld Convention* -
http://ausdwcon.org
"The Discworld Grand Tour" - Adelaide SA, August 4-6, 2017

-- 
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] The Orderable "move" buttons

[Stephen McDonald]

On Fri, May 15, 2015 at 7:45 AM, Danny  wrote:

> Hi all,
>
> I'm doing a new development using Mezzanine master and Django 1.8.1, and
> I've got a model that derives from Orderable,
> with appropriate admin stuff set up for it too.
>
> In Mezzanine 3.1.10, the "_order" field was just an integer, so it was
> easy to edit, but with the latest mezzanine, it's now been replaced with
> the wonderful drag-and-drop arrows. Except, for my new model, they don't
> drag and drop!
>

These have always been drag/drop - the previous behaviour you've seen was a
bug. Likely candidate is JavaScript not being hosted correctly. Anyway
you're now seeing what should have always worked :-)


>
> Is there something I'm missing with respect to admin setup, or
> templates/css/js that I need to add so that the new model has the same
> drag/drop functionality as e.g. pages or the inlines for form fields?
>

Take a look at the models and admin classes in mezzanine.forms that makes
full use of this, particularly the admin class for your inlines:
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/forms/admin.py#L38


>
> I did have a look at, e.g.
> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/static/mezzanine/js/admin/dynamic_inline.js#L43
> but am not sure if there's something subtle I'm missing that I need to do
> to make it work.
> Is it possible I need to install grapelli_safe from github master as well?
> (I haven't done that yet, just using what's on PyPi)
>
> Thanks,
>
> Seeya. Danny.
>
> --
> 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] The Orderable "move" buttons

[Danny]

Hi all,

I'm doing a new development using Mezzanine master and Django 1.8.1, and 
I've got a model that derives from Orderable,

with appropriate admin stuff set up for it too.

In Mezzanine 3.1.10, the "_order" field was just an integer, so it was 
easy to edit, but with the latest mezzanine, it's now been replaced with 
the wonderful drag-and-drop arrows. Except, for my new model, they don't 
drag and drop!


Is there something I'm missing with respect to admin setup, or 
templates/css/js that I need to add so that the new model has the same 
drag/drop functionality as e.g. pages or the inlines for form fields?


I did have a look at, e.g. 
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/static/mezzanine/js/admin/dynamic_inline.js#L43 
but am not sure if there's something subtle I'm missing that I need to 
do to make it work.
Is it possible I need to install grapelli_safe from github master as 
well? (I haven't done that yet, just using what's on PyPi)


Thanks,

Seeya. Danny.

--
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] Real Time update of orders

[Stephen McDonald]

Well thanks for actually clarifying what you're trying to do.

As others said if you can get away with AJAX it'll be a lot easier.
Otherwise if the __bases__ hacks I mentioned don't work, it's certainly
feasible to create a tiny websocket pubsub server using
gevent+gunicorn+redis without any frameworks. I've done it on a handful of
projects and the following code is the basic shell of what I use:

https://gist.github.com/stephenmcd/d7551ba68d01b1d889d2

Provided as is without any support, but everything you need is there :-)


On Thu, May 14, 2015 at 10:03 AM, Andrew Fam  wrote:

> Hey Stephen thanks for this.
>
> Yes I understand AJAX and a real time update.
>
> The store I"m working with sells quite fast moving products and needed a
> consolidated orders view that would be automatically updated once orders
> came in.
> So, instead of having to click refresh the page to see the new orders, I
> was looking for a way for the page to update once a new order came in.
>
> Best regards,
> Andrew
>
>
> On Sunday, May 10, 2015 at 7:03:58 AM UTC+8, Stephen McDonald wrote:
>>
>> Hi there,
>>
>> "real time" is incredibly vague and begs for a stricter definition. The
>> true meaning indicates a guaranteed response time, which is most likely not
>> what your client means (http://en.wikipedia.org/wiki/Real-time_computing
>> ).
>>
>> What they most likely mean is "submits without reloading the page", in
>> which case, rather than introducing a whole separate moving part into your
>> stack (a websocket server), along with what appears to be another
>> framework, you could achieve the desired result simply by making an AJAX
>> request in the checkout process.
>>
>> If unfortunately your client actually means "has to use websockets", then
>> you might be able monkey-patch the relevant model doing something like:
>>
>> Foo.__bases__ = (SelfPublishModel,) + Foo.__bases__
>>
>> But before you go down that path I think you'd do yourself and your
>> client a favour by educating them on using the best tool for the job rather
>> than having them dictate your architecture to you :-)
>>
>> Good luck!
>>
>>
>>
>> On Sat, May 9, 2015 at 2:57 PM, Andrew Fam  wrote:
>>
>>> I'm thinking of using mezzanine but a client wants a real time update of
>>> orders.
>>>
>>> http://swampdragon.net/documentation/quick-start/
>>>
>>> from django.db import modelsfrom swampdragon.models import 
>>> SelfPublishModelfrom .serializers import FooSerializer
>>>
>>> class Foo(SelfPublishModel, models.Model):
>>> serializer_class = FooSerializer
>>> text = models.CharField(max_length=100)
>>>
>>>
>>> Got this off the swampdragon page and they require an addition of
>>> SelfPublishModel to any object that you need realtime support.
>>> Any idea how to do this with cartridge?
>>>
>>>
>>> Best regarsd,
>>> Andrew
>>>
>>> --
>>> 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.
>>>
>>
>>
>>
>> --
>> 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.
>



-- 
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: Introducing Mezzanine's Core Development Team

[Pushkar Paranjpe]

Congrats team core! Looking forward to lots of mezzanining !

On Thursday, 14 May 2015 22:32:02 UTC+5:30, Zbyszek Lupikasza wrote:
>
> Great news!
> And congratulations.
> Now I'm sure my decision to go Mezzanine from Drupal and Wordpress was 
> right and soon Mezzanine will have huge community, at least the same size 
> as Drupal and WP!
>

-- 
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] Error importing from wordpress

[Josh Cartmell]

Glad you got it working =)

If you figure anything more out and can demonstrate the error let us know
(or even submit a pull request to the wordpress importer), we are always
looking to improve!


On Thu, May 14, 2015 at 12:34 PM, Jonathan Sandoval 
wrote:

> Ohh, the new problem is related to a print because of the verbosity. It
> was going to print the new category, but it has a "acute accent" (I think
> it's the right translation for tilde). I set the verbosity level to 0 and
> it worked.
>
> Anyway, I had other problems with spanish accents if I introduced them
> while importing. Anyway, I ignored them for now.
>
>
> El jueves, 14 de mayo de 2015, 11:29:52 (UTC-5), Jonathan Sandoval
> escribió:
>>
>> Many thanks Josh. I modified the code directly and it [almost worked].
>> Now I'm getting the following exception:
>>
>> Traceback (most recent call last):
>>   File "manage.py", line 28, in 
>> execute_from_command_line(sys.argv)
>>   File
>> "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/__init__.py"
>> , line 399, in execute_from_command_line
>> utility.execute()
>>   File
>> "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/__init__.py"
>> , line 392, in execute
>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>   File
>> "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/base.py"
>> , line 242, in run_from_argv
>> self.execute(*args, **options.__dict__)
>>   File
>> "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/base.py"
>> , line 285, in execute
>> output = self.handle(*args, **options)
>>   File
>> "/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/blog/management/base.py"
>> , line 190, in handle
>> print("Imported category: %s" % cat)
>> UnicodeEncodeError: 'ascii' codec can't encode character '\xed' in
>> position 30: ordinal not in range(128)
>>
>> Anyway, I'll try to compare with the new version of the file to see if
>> it's already fixed. I think the problem is related to spanish characters,
>> because the wordpress posts, categories and tags are written in spanish.
>>
>> Again, many thanks.
>>
>> El jueves, 14 de mayo de 2015, 10:55:33 (UTC-5), Josh Cartmell escribió:
>>>
>>> Hi Jonathan, I don't think it's made it onto pypi yet, but the way that
>>> pub_date is converted for use in Mezzanine was updated fairly recently
>>> because of changes in Wordpress' export XML.  Take a look at it now:
>>>
>>> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/blog/management/commands/import_wordpress.py#L63
>>>
>>> Since this change will be making it into Mezzanine with the next release
>>> I think it would be safe to replace the old version with the new one,
>>> directly in your copy of Mezzanine.  If you ever upgrade you will get the
>>> new version anyways so I think this is one case where directly modifying
>>> Mezzanine would be ok.
>>>
>>> Good luck!
>>>
>>> On Thu, May 14, 2015 at 11:28 AM, Jonathan Sandoval >> > wrote:
>>>
 Hi.
 I want to migrate from wordpress 3.9.6 to mezzanine. I just installed
 mezzanine and I exported the wordpress posts and pages and, when trying to
 import the xml I get the following error:

 /home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/utils/
 conf.py:52: UserWarning: You haven't defined the ALLOWED_HOSTS
 settings, which Django 1.5 requires. Will fall back to the domains
 configured as sites.
   warn("You haven't defined the ALLOWED_HOSTS settings, which "
 /home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/utils/conf.py:60:
 UserWarning: TIME_ZONE setting is not set, using closest match: US/Eastern
   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
 /home/ark/corriente/venv/lib/python3.4/site-packages/feedparser.py:346:
 DeprecationWarning: To avoid breaking existing software while fixing issue
 310, a temporary mapping has been created from `updated_parsed` to
 `published_parsed` if `updated_parsed` doesn't exist. This fallback will be
 removed in a future version of feedparser.
   DeprecationWarning)

 Traceback (most recent call last):
   File "manage.py", line 28, in 
 execute_from_command_line(sys.argv)
   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/
 core/management/__init__.py", line 399, in execute_from_command_line
 utility.execute()
   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/
 core/management/__init__.py", line 392, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/
 core/management/base.py", line 242, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/
 core/management/base.py", line 

Re: [mezzanine-users] Error with spanish characters

[Eduardo Rivas]

Glad you could sort it out :)

--
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] Error with spanish characters

[Jonathan Sandoval]

The problem occured with new posts to. I just changed the locales in my OS 
and that fixed the problem. 

Many thanks for the help and advice Eduardo.

El jueves, 14 de mayo de 2015, 12:31:48 (UTC-5), Eduardo Rivas escribió:
>
> Ah, ok. See if your OS level and database locales include Spanish. 
>
> Also, create a blog post with special characters in the Mezzanine admin 
> to see if it also raises the exception. Perhaps it is an issue only with 
> imported posts. 
>

-- 
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] Error with spanish characters

[Eduardo Rivas]

Ah, ok. See if your OS level and database locales include Spanish.

Also, create a blog post with special characters in the Mezzanine admin 
to see if it also raises the exception. Perhaps it is an issue only with 
imported posts.


--
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] Error with spanish characters

[Jonathan Sandoval]

Hi Eduardo.
I'm running the django development server (I'm running it with python 
manage.py runserver 0.0.0.0:8000).

Right now I'm migrating the old blog, so, I'm just trying to adjust the 
theme, categories, and so on. I have not configured gunicorn or uwsgi yet.

El jueves, 14 de mayo de 2015, 12:14:45 (UTC-5), Eduardo Rivas escribió:
>
> Hi Jonathan. 
>
> Are you using the Django development server, or a standalone application 
> server (gunicorn, uwsgi, Apache, etc)? 
>
> I've encountered similar errors when running outside the development 
> server, and the fix was to enable the appropriate locales in the server 
> configuration. 
>

-- 
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] Error with spanish characters

[Eduardo Rivas]

Hi Jonathan.

Are you using the Django development server, or a standalone application 
server (gunicorn, uwsgi, Apache, etc)?


I've encountered similar errors when running outside the development 
server, and the fix was to enable the appropriate locales in the server 
configuration.


--
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] Error with spanish characters

[Jonathan Sandoval]

Hi everyone.
I recently installed mezzanine from pip and imported a spanish wordpress 
blog I had. With some help from this list I managed to import the 
information, but, as I have posts in spanish where the titles have accents 
(for example: "investigación"), I get the following error when I try to see 
that blog post:

UnicodeEncodeError at /blog/la-academia-se-volvió-un-negocio-no-es-ciencia/ 
'ascii' codec can't encode character '\xf3' in position 82: ordinal not in 
range(128)
 
 Request Method: GET 
 Request URL: 
http://example.org:8000/blog/la-academia-se-volvi%C3%B3-un-negocio-no-es-ciencia/
 

 Django Version: 1.6.11 
 Exception Type: UnicodeEncodeError 
 Exception Value: 'ascii' codec can't encode character '\xf3' in position 82
: ordinal not in range(128)
 
 Exception Location: /home/ark/corriente/venv/lib/python3.4/site-packages/
django/template/loaders/filesystem.py in load_template_source, line 37 
 Python Executable: /home/ark/corriente/venv/bin/python 
 Python Version: 3.4.2 
 Python Path: ['/home/ark/corriente/corriente',
 '/home/ark/corriente/venv/lib/python3.4',
 '/home/ark/corriente/venv/lib/python3.4/plat-x86_64-linux-gnu',
 '/home/ark/corriente/venv/lib/python3.4/lib-dynload',
 '/usr/lib/python3.4',
 '/usr/lib/python3.4/plat-x86_64-linux-gnu',
 '/home/ark/corriente/venv/lib/python3.4/site-packages',
 '/home/ark/corriente']
 
 Server time: Jue, 14 May 2015 12:55:57 -0400


¿Is this a bug, or maybe I'm doing something wrong?. It only happens with 
posts with these characters.

Thanks for any help·

-- 
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: Introducing Mezzanine's Core Development Team

[Zbyszek Lupikasza]

Great news!
And congratulations.
Now I'm sure my decision to go Mezzanine from Drupal and Wordpress was 
right and soon Mezzanine will have huge community, at least the same size 
as Drupal and WP!

-- 
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] Error importing from wordpress

[Jonathan Sandoval]

Ohh, the new problem is related to a print because of the verbosity. It was 
going to print the new category, but it has a "acute accent" (I think it's 
the right translation for tilde). I set the verbosity level to 0 and it 
worked.

Anyway, I had other problems with spanish accents if I introduced them 
while importing. Anyway, I ignored them for now.

El jueves, 14 de mayo de 2015, 11:29:52 (UTC-5), Jonathan Sandoval escribió:
>
> Many thanks Josh. I modified the code directly and it [almost worked].  
> Now I'm getting the following exception:
>
> Traceback (most recent call last):
>   File "manage.py", line 28, in 
> execute_from_command_line(sys.argv)
>   File 
> "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/__init__.py"
> , line 399, in execute_from_command_line
> utility.execute()
>   File 
> "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/__init__.py"
> , line 392, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File 
> "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/base.py"
> , line 242, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File 
> "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/base.py"
> , line 285, in execute
> output = self.handle(*args, **options)
>   File 
> "/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/blog/management/base.py"
> , line 190, in handle
> print("Imported category: %s" % cat)
> UnicodeEncodeError: 'ascii' codec can't encode character '\xed' in 
> position 30: ordinal not in range(128)
>
> Anyway, I'll try to compare with the new version of the file to see if 
> it's already fixed. I think the problem is related to spanish characters, 
> because the wordpress posts, categories and tags are written in spanish.
>
> Again, many thanks.
>
> El jueves, 14 de mayo de 2015, 10:55:33 (UTC-5), Josh Cartmell escribió:
>>
>> Hi Jonathan, I don't think it's made it onto pypi yet, but the way that 
>> pub_date is converted for use in Mezzanine was updated fairly recently 
>> because of changes in Wordpress' export XML.  Take a look at it now:
>>
>> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/blog/management/commands/import_wordpress.py#L63
>>
>> Since this change will be making it into Mezzanine with the next release 
>> I think it would be safe to replace the old version with the new one, 
>> directly in your copy of Mezzanine.  If you ever upgrade you will get the 
>> new version anyways so I think this is one case where directly modifying 
>> Mezzanine would be ok.
>>
>> Good luck!
>>
>> On Thu, May 14, 2015 at 11:28 AM, Jonathan Sandoval  
>> wrote:
>>
>>> Hi.
>>> I want to migrate from wordpress 3.9.6 to mezzanine. I just installed 
>>> mezzanine and I exported the wordpress posts and pages and, when trying to 
>>> import the xml I get the following error:
>>>
>>> /home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/utils/
>>> conf.py:52: UserWarning: You haven't defined the ALLOWED_HOSTS 
>>> settings, which Django 1.5 requires. Will fall back to the domains 
>>> configured as sites.
>>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>>> /home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/utils/conf.py:60:
>>>  
>>> UserWarning: TIME_ZONE setting is not set, using closest match: US/Eastern
>>>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
>>> /home/ark/corriente/venv/lib/python3.4/site-packages/feedparser.py:346: 
>>> DeprecationWarning: To avoid breaking existing software while fixing issue 
>>> 310, a temporary mapping has been created from `updated_parsed` to 
>>> `published_parsed` if `updated_parsed` doesn't exist. This fallback will be 
>>> removed in a future version of feedparser.
>>>   DeprecationWarning)
>>>
>>> Traceback (most recent call last):
>>>   File "manage.py", line 28, in 
>>> execute_from_command_line(sys.argv)
>>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core
>>> /management/__init__.py", line 399, in execute_from_command_line
>>> utility.execute()
>>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core
>>> /management/__init__.py", line 392, in execute
>>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core
>>> /management/base.py", line 242, in run_from_argv
>>> self.execute(*args, **options.__dict__)
>>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core
>>> /management/base.py", line 285, in execute
>>> output = self.handle(*args, **options)
>>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/
>>> blog/management/base.py", line 167, in handle
>>> self.handle_import(options)
>>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/
>>> blog/management/commands/im

Re: [mezzanine-users] Error importing from wordpress

[Jonathan Sandoval]

Many thanks Josh. I modified the code directly and it [almost worked].  Now 
I'm getting the following exception:

Traceback (most recent call last):
  File "manage.py", line 28, in 
execute_from_command_line(sys.argv)
  File 
"/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/__init__.py"
, line 399, in execute_from_command_line
utility.execute()
  File 
"/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/__init__.py"
, line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/base.py"
, line 242, in run_from_argv
self.execute(*args, **options.__dict__)
  File 
"/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/management/base.py"
, line 285, in execute
output = self.handle(*args, **options)
  File 
"/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/blog/management/base.py"
, line 190, in handle
print("Imported category: %s" % cat)
UnicodeEncodeError: 'ascii' codec can't encode character '\xed' in position 
30: ordinal not in range(128)

Anyway, I'll try to compare with the new version of the file to see if it's 
already fixed. I think the problem is related to spanish characters, 
because the wordpress posts, categories and tags are written in spanish.

Again, many thanks.

El jueves, 14 de mayo de 2015, 10:55:33 (UTC-5), Josh Cartmell escribió:
>
> Hi Jonathan, I don't think it's made it onto pypi yet, but the way that 
> pub_date is converted for use in Mezzanine was updated fairly recently 
> because of changes in Wordpress' export XML.  Take a look at it now:
>
> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/blog/management/commands/import_wordpress.py#L63
>
> Since this change will be making it into Mezzanine with the next release I 
> think it would be safe to replace the old version with the new one, 
> directly in your copy of Mezzanine.  If you ever upgrade you will get the 
> new version anyways so I think this is one case where directly modifying 
> Mezzanine would be ok.
>
> Good luck!
>
> On Thu, May 14, 2015 at 11:28 AM, Jonathan Sandoval  > wrote:
>
>> Hi.
>> I want to migrate from wordpress 3.9.6 to mezzanine. I just installed 
>> mezzanine and I exported the wordpress posts and pages and, when trying to 
>> import the xml I get the following error:
>>
>> /home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/utils/conf
>> .py:52: UserWarning: You haven't defined the ALLOWED_HOSTS settings, 
>> which Django 1.5 requires. Will fall back to the domains configured as 
>> sites.
>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>> /home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/utils/conf.py:60:
>>  
>> UserWarning: TIME_ZONE setting is not set, using closest match: US/Eastern
>>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
>> /home/ark/corriente/venv/lib/python3.4/site-packages/feedparser.py:346: 
>> DeprecationWarning: To avoid breaking existing software while fixing issue 
>> 310, a temporary mapping has been created from `updated_parsed` to 
>> `published_parsed` if `updated_parsed` doesn't exist. This fallback will be 
>> removed in a future version of feedparser.
>>   DeprecationWarning)
>>
>> Traceback (most recent call last):
>>   File "manage.py", line 28, in 
>> execute_from_command_line(sys.argv)
>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
>> management/__init__.py", line 399, in execute_from_command_line
>> utility.execute()
>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
>> management/__init__.py", line 392, in execute
>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
>> management/base.py", line 242, in run_from_argv
>> self.execute(*args, **options.__dict__)
>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
>> management/base.py", line 285, in execute
>> output = self.handle(*args, **options)
>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/
>> blog/management/base.py", line 167, in handle
>> self.handle_import(options)
>>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/
>> blog/management/commands/import_wordpress.py", line 64, in handle_import
>> pub_date = datetime.fromtimestamp(mktime(pub_date))
>> TypeError: Tuple or struct_time argument required
>>
>>
>> Thanks for any help provided.
>>
>> -- 
>> 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 subscrib

Re: [mezzanine-users] Real Time update of orders

[Brandon Keith Biggs]

Hello,
If you did not want to write in Javascript, you can alternatively do an 
ajax call using python in brython:

http://brython.info/doc/en/index.html#
it is under
Brython-specific built-in modules / browser.ajax

Although I would first read all the stuff under
Browser interface
if you have not yet used brython.

It will look the same to the user, it will just be in python and its 
built-in modules rather than javascript and its strange syntax.

thanks,

Brandon Keith Biggs 
On 5/14/2015 5:43 PM, Josh Cartmell wrote:
Hi Andrew, I would set up some javascript that would make an ajax call 
every 5, 10, 30 seconds (whatever interval works for you) and then 
would update the orders on the page if any new ones had come in.


I think that would be much easier to set up than trying to make things 
literally real time.  Even websockets will have latency so nothing is 
truly real time, just an approximation. The question is how good of an 
approximation you need to have.


To make this more efficient you could have your javascript store the 
most recent order number, then on whatever interval you decide it 
makes a call that only checks what the most recent order number is in 
the database.  If it has changed from what you had stored you then 
make a separate call that reloads the orders (or just loads the newest 
ones).


On Wed, May 13, 2015 at 8:03 PM, Andrew Fam > wrote:


Hey Stephen thanks for this.

Yes I understand AJAX and a real time update.

The store I"m working with sells quite fast moving products and
needed a consolidated orders view that would be automatically
updated once orders came in.
So, instead of having to click refresh the page to see the new
orders, I was looking for a way for the page to update once a new
order came in.

Best regards,
Andrew


On Sunday, May 10, 2015 at 7:03:58 AM UTC+8, Stephen McDonald wrote:

Hi there,

"real time" is incredibly vague and begs for a stricter
definition. The true meaning indicates a guaranteed response
time, which is most likely not what your client means
(http://en.wikipedia.org/wiki/Real-time_computing).

What they most likely mean is "submits without reloading the
page", in which case, rather than introducing a whole separate
moving part into your stack (a websocket server), along with
what appears to be another framework, you could achieve the
desired result simply by making an AJAX request in the
checkout process.

If unfortunately your client actually means "has to use
websockets", then you might be able monkey-patch the relevant
model doing something like:

Foo.__bases__ = (SelfPublishModel,) + Foo.__bases__

But before you go down that path I think you'd do yourself and
your client a favour by educating them on using the best tool
for the job rather than having them dictate your architecture
to you :-)

Good luck!



On Sat, May 9, 2015 at 2:57 PM, Andrew Fam
 wrote:

I'm thinking of using mezzanine but a client wants a real
time update of orders.

http://swampdragon.net/documentation/quick-start/

from  django.db  import  models
from  swampdragon.models  import  SelfPublishModel
from  .serializers  import  FooSerializer


class  Foo(SelfPublishModel,  models.Model):
 serializer_class  =  FooSerializer
 text  =  models.CharField(max_length=100)


Got this off the swampdragon page and they require an
addition of SelfPublishModel to any object that you need
realtime support.
Any idea how to do this with cartridge?


Best regarsd,
Andrew
-- 
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.




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


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

Re: [mezzanine-users] Error importing from wordpress

[Josh Cartmell]

Hi Jonathan, I don't think it's made it onto pypi yet, but the way that
pub_date is converted for use in Mezzanine was updated fairly recently
because of changes in Wordpress' export XML.  Take a look at it now:
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/blog/management/commands/import_wordpress.py#L63

Since this change will be making it into Mezzanine with the next release I
think it would be safe to replace the old version with the new one,
directly in your copy of Mezzanine.  If you ever upgrade you will get the
new version anyways so I think this is one case where directly modifying
Mezzanine would be ok.

Good luck!

On Thu, May 14, 2015 at 11:28 AM, Jonathan Sandoval 
wrote:

> Hi.
> I want to migrate from wordpress 3.9.6 to mezzanine. I just installed
> mezzanine and I exported the wordpress posts and pages and, when trying to
> import the xml I get the following error:
>
> /home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/utils/conf.
> py:52: UserWarning: You haven't defined the ALLOWED_HOSTS settings, which
> Django 1.5 requires. Will fall back to the domains configured as sites.
>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
> /home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/utils/conf.py:60:
> UserWarning: TIME_ZONE setting is not set, using closest match: US/Eastern
>   warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
> /home/ark/corriente/venv/lib/python3.4/site-packages/feedparser.py:346:
> DeprecationWarning: To avoid breaking existing software while fixing issue
> 310, a temporary mapping has been created from `updated_parsed` to
> `published_parsed` if `updated_parsed` doesn't exist. This fallback will be
> removed in a future version of feedparser.
>   DeprecationWarning)
>
> Traceback (most recent call last):
>   File "manage.py", line 28, in 
> execute_from_command_line(sys.argv)
>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
> management/__init__.py", line 399, in execute_from_command_line
> utility.execute()
>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
> management/__init__.py", line 392, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
> management/base.py", line 242, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
> management/base.py", line 285, in execute
> output = self.handle(*args, **options)
>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/
> blog/management/base.py", line 167, in handle
> self.handle_import(options)
>   File "/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/
> blog/management/commands/import_wordpress.py", line 64, in handle_import
> pub_date = datetime.fromtimestamp(mktime(pub_date))
> TypeError: Tuple or struct_time argument required
>
>
> Thanks for any help provided.
>
> --
> 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] Real Time update of orders

[Josh Cartmell]

Hi Andrew, I would set up some javascript that would make an ajax call
every 5, 10, 30 seconds (whatever interval works for you) and then would
update the orders on the page if any new ones had come in.

I think that would be much easier to set up than trying to make things
literally real time.  Even websockets will have latency so nothing is truly
real time, just an approximation.  The question is how good of an
approximation you need to have.

To make this more efficient you could have your javascript store the most
recent order number, then on whatever interval you decide it makes a call
that only checks what the most recent order number is in the database.  If
it has changed from what you had stored you then make a separate call that
reloads the orders (or just loads the newest ones).

On Wed, May 13, 2015 at 8:03 PM, Andrew Fam  wrote:

> Hey Stephen thanks for this.
>
> Yes I understand AJAX and a real time update.
>
> The store I"m working with sells quite fast moving products and needed a
> consolidated orders view that would be automatically updated once orders
> came in.
> So, instead of having to click refresh the page to see the new orders, I
> was looking for a way for the page to update once a new order came in.
>
> Best regards,
> Andrew
>
>
> On Sunday, May 10, 2015 at 7:03:58 AM UTC+8, Stephen McDonald wrote:
>>
>> Hi there,
>>
>> "real time" is incredibly vague and begs for a stricter definition. The
>> true meaning indicates a guaranteed response time, which is most likely not
>> what your client means (http://en.wikipedia.org/wiki/Real-time_computing
>> ).
>>
>> What they most likely mean is "submits without reloading the page", in
>> which case, rather than introducing a whole separate moving part into your
>> stack (a websocket server), along with what appears to be another
>> framework, you could achieve the desired result simply by making an AJAX
>> request in the checkout process.
>>
>> If unfortunately your client actually means "has to use websockets", then
>> you might be able monkey-patch the relevant model doing something like:
>>
>> Foo.__bases__ = (SelfPublishModel,) + Foo.__bases__
>>
>> But before you go down that path I think you'd do yourself and your
>> client a favour by educating them on using the best tool for the job rather
>> than having them dictate your architecture to you :-)
>>
>> Good luck!
>>
>>
>>
>> On Sat, May 9, 2015 at 2:57 PM, Andrew Fam  wrote:
>>
>>> I'm thinking of using mezzanine but a client wants a real time update of
>>> orders.
>>>
>>> http://swampdragon.net/documentation/quick-start/
>>>
>>> from django.db import modelsfrom swampdragon.models import 
>>> SelfPublishModelfrom .serializers import FooSerializer
>>>
>>> class Foo(SelfPublishModel, models.Model):
>>> serializer_class = FooSerializer
>>> text = models.CharField(max_length=100)
>>>
>>>
>>> Got this off the swampdragon page and they require an addition of
>>> SelfPublishModel to any object that you need realtime support.
>>> Any idea how to do this with cartridge?
>>>
>>>
>>> Best regarsd,
>>> Andrew
>>>
>>> --
>>> 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.
>>>
>>
>>
>>
>> --
>> 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.
>

-- 
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] Error importing from wordpress

[Jonathan Sandoval]

Hi.
I want to migrate from wordpress 3.9.6 to mezzanine. I just installed 
mezzanine and I exported the wordpress posts and pages and, when trying to 
import the xml I get the following error:

/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/utils/conf.py
:52: UserWarning: You haven't defined the ALLOWED_HOSTS settings, which 
Django 1.5 requires. Will fall back to the domains configured as sites.
  warn("You haven't defined the ALLOWED_HOSTS settings, which "
/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/utils/conf.py:60:
 
UserWarning: TIME_ZONE setting is not set, using closest match: US/Eastern
  warn("TIME_ZONE setting is not set, using closest match: %s" % tz)
/home/ark/corriente/venv/lib/python3.4/site-packages/feedparser.py:346: 
DeprecationWarning: To avoid breaking existing software while fixing issue 
310, a temporary mapping has been created from `updated_parsed` to 
`published_parsed` if `updated_parsed` doesn't exist. This fallback will be 
removed in a future version of feedparser.
  DeprecationWarning)

Traceback (most recent call last):
  File "manage.py", line 28, in 
execute_from_command_line(sys.argv)
  File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
management/__init__.py", line 399, in execute_from_command_line
utility.execute()
  File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
management/__init__.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
management/base.py", line 242, in run_from_argv
self.execute(*args, **options.__dict__)
  File "/home/ark/corriente/venv/lib/python3.4/site-packages/django/core/
management/base.py", line 285, in execute
output = self.handle(*args, **options)
  File "/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/blog/
management/base.py", line 167, in handle
self.handle_import(options)
  File "/home/ark/corriente/venv/lib/python3.4/site-packages/mezzanine/blog/
management/commands/import_wordpress.py", line 64, in handle_import
pub_date = datetime.fromtimestamp(mktime(pub_date))
TypeError: Tuple or struct_time argument required


Thanks for any help provided.

-- 
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: Introducing Mezzanine's Core Development Team

[Mario Gudelj]

Congrats everyone! I think you're in charge of the most important django 
project atm.

On Tuesday, May 12, 2015 at 7:20:44 AM UTC+10, Stephen McDonald wrote:
>
> Hi all,
>
> Today I'm thrilled to announce the introduction of a core development team 
> for Mezzanine. I've written a detailed post about it, please heave a read:
>
>
> http://blog.jupo.org/2015/05/11/introducing-mezzanines-core-development-team/
>
> TLDR: The new team consists of myself, Josh Cartmell, Ken Bolton, Alex 
> Hill, Ed Rivas, Mathias Ettinger, who have each made huge contributions to 
> the project over several years.
>
> Please join me in welcoming them!
>
>
> -- 
> 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.