Re: [mezzanine-users] deploying Mezzanine to a VPS

; >> ImportError: cannot import name 'isMappingType' >> >> > On Friday, August 17, 2018 at 9:26:04 PM UTC+4:30, Eduardo Rivas wrote: >> >> Try using Fabric version 1: pip install -U “fabric<2” >> >> >> >> *From: *Kenneth L Bolton >&

RE: [mezzanine-users] deploying Mezzanine to a VPS

Try using Fabric version 1: pip install -U “fabric<2” From: Kenneth L Bolton Sent: Friday, August 17, 2018 10:42 AM To: mezzanine-users@googlegroups.com Subject: Re: [mezzanine-users] deploying Mezzanine to a VPS

RE: [mezzanine-users] Admin redirect not working

Make sure the URL you’re trying to redirect is not assigned to a Page or any view. The redirects will only kick in if the URL raises a 404. From: Travis Sent: Sunday, August 26, 2018 5:57 PM To: Mezzanine Users Subject: [mezzanine-users] Admin redirect not working Anyone having issues with the

RE: [mezzanine-users] Want to integrate a wiki?

Just my two cents: - You could fork Mezzanine Wiki or contribute back to it to update it to support the latest version of Mezzanine. - You can use Django apps and add them to your Mezzanine project, no need to abandon Mezzanine to use them. From: John Whitmore Sent: Friday, August 31, 2018

Re: [mezzanine-users] Modifying behavior of TimeStamped `updated` timestamp for subclasses

Haven't tried this but I think it should work. It is an extra DB table but doesn't require monkey patching anything and it can leave in its own app: Create a new model called LastUpdate or TimeStamp, with a datetime field and a generic relation

Re: [mezzanine-users] Re: What's wrong in my local_settings / how to do basic deploy to aws

Hi Wolfgang. Production and development databases are kept separate, as well as media uploads. If you'd like to upload your database and media files from dev to prod you can add custom fabric tasks that do so. On 2018-04-23 1:13 PM, Wolfgang M wrote: You were perfectly right Christian. I

RE: [mezzanine-users] Move the deployment to new VPS along with thecontents

You’ll need to create a database dump, copy it over to the new server, and restore it. If you’re using postgres the commands are pg_dump and pg_restore. You’ll also need to move media files. I recommend you use rsync from one server to the other. The folder you want to copy is

RE: [mezzanine-users] Move the deployment to new VPS along withthecontents

. I am a bit worried about the security stuff. On Tuesday, October 16, 2018 at 5:52:37 PM UTC+3:30, Eduardo Rivas wrote: You’ll need to create a database dump, copy it over to the new server, and restore it. If you’re using postgres the commands are pg_dump and pg_restore.   You’ll also need to move

RE: [mezzanine-users] the www and non-www version of my deployment aredifferent

Mezzanine can serve different sites depending on the domain. You have two site records in your database, one for www and another for non-www. All content (pages, blog posts, etc) is independent from one site to the other. One site is probably empty (no content) and that’s why it looks weird

Re: [mezzanine-users] Static files give 404 if debug == False

Hi Christer. The collectstatic command is a Django concept, not something specific to Mezzanine. Even though it requires more time, a strong foundation on Django will make your time with Mezzanine much more productive. When you use Django's dev server, it will look into the /static directory

Re: [mezzanine-users] Moving information from the development area to production....

That's correct, production and development databases are not related at all. What I usually do is create a dump of the dev DB and restore it on the production server. You'll also need to upload media files as those are separate as well. On Sun, Mar 24, 2019, 11:48 AM Bobby Neal wrote: > >

RE: [mezzanine-users] Draft show up in View All Posts

Hi Bithja. Admin users will always see all posts. Have you tried looking at the site without being logged in? From: Bithja Feuersenger Sent: Friday, February 15, 2019 12:07 PM To: Mezzanine Users Subject: [mezzanine-users] Draft show up in View All Posts Hi all, Is it normal for blog post

RE: [mezzanine-users] Re: Multiple Blogs

all the contents from mezzanine.blog, do you also mean the models.py and how without getting an error? Kind regards, Jesper fredag den 10. august 2018 kl. 20.18.27 UTC+2 skrev Eduardo Rivas: Sorry, don’t have enough time to write a code sample right now, but here is a more detailed description

RE: [mezzanine-users] Newbe question on Creating Custom Content

Hi Larry. You’re correct; the tutorial assumes you’re comfortable writing Django applications. In this particular instance it assumes you have an app (a top-level directory, let’s call it “authors”) and you’d add the code to “authors/models.py” and “authors/admin.py”. I recommend you go over

RE: [mezzanine-users] Page and Site SQL Gets Triggered with View LevelCaching

Hi Matt. My guess is that Mezzanine’s Page middleware tries to fetch a page on every request (as pages can have any URL). I would try to disable the middlewares you don’t need and see if that works. From: Matt Mansour Sent: Wednesday, July 24, 2019 10:05 AM To: Mezzanine Users Subject:

RE: [mezzanine-users] Migration to Jazzband / Code Shelter

Hi Pete, Thanks for bringing this over to the mailing list. I’m one of the contributors to Mezzanine and still use it almost daily. I’m glad others still want to see the project move forward. Do Jazzband or Code Shelter have contributors on standby ready to take in projects and perform maintenance

[mezzanine-users] Are fabric deployments popular?

Hello everyone, I'm Ed, one of the collaborators helping maintain Mezzanine. As we prepare to release the next version of Mezzanine (supporting Python 3 and Django 2.2 only) an issue was recently filed wondering about the future of

RE: Re: [mezzanine-users] Are fabric deployments popular?

on the forums. I would suggest having multiple fab files though, for different types of  infrastructure. For example, one for normal rsync, one for git, one for Amazon web services etc. Thanks for all your hard work and help on the forums Ed! RegardsRoger On Wed, 19 Feb 2020 at 01:16, Eduardo Rivas <jerivas

[mezzanine-users] Mezzanine 5.0 alpha 1 released!

Hello everyone! I'm very happy to announce that the first pre-release of the next major version of Mezzanine is now available: 5.0.0 alpha 1. You can download it right now with `pip install -U mezzanine==5.0.0a1`. This will also get you the alpha versions for filebrowser-safe and

Re: [mezzanine-users] Re: Mezzanine 5.0 alpha 1 released!

Installing the alpha is not the same as installing from the master branch. The alpha doesn't need to be built, it can be installed directly: pip install -U mezzanine==5.0.0a1 On Tue, Feb 16, 2021, 3:29 PM Michael Babcock wrote: > Finally decided to check this out and this might be a stupid

[mezzanine-users] Deprecating Google Groups in favor of GitHub Discussions

Hello everyone  This is a quick announcement about my intention to make GitHub Discussions (https://github.com/stephenmcd/mezzanine/discussions) the official forum platform for Mezzanine. Having the forum and the code live under the same platform makes managing them easier, specially when it

<    1   2   3   4