Hi Wesley,
In general, developers should avoid making changes directly to the stack,
whether it is Cartridge, Mezzanine, Django, or Python. Instead, changes are
made in files that are isolated from the primary stack. This allows the
developer to arbitrarily upgrade parts of the stack without
I've posted how I made Mezzanine + AngularJS in HTML5 mode to work *here
http://stackoverflow.com/a/26000332/236169*.
On Sunday, June 1, 2014 1:29:38 PM UTC-4, Fredrik Blomqvist wrote:
Hi,
I want to create a website that uses both Mezzanine as its CMS and Angular
for the user experience
Ken
What is django's groups? Is that part of Mezzanine? Can you please give me
link. Thanks in advance
On Monday, September 22, 2014 7:35:43 AM UTC-4, Kenneth Bolton wrote:
I have done exactly what you are looking for using stock
Mezzanine/Cartridge. Do not over-think the problem. Use
Walter: Thanks but chatroll seems more appropriate as an add-on to sites
for providing sales/customer support.
Kenneth: Thanks. I like Gnotty, though it seems I have to edit the code
On Sunday, September 21, 2014 3:05:15 AM UTC-4, vtx...@gmail.com wrote:
Hello
I want to have a real time
1. Can I use django-bootstrap-themes (
https://www.djangopackages.com/packages/p/django-bootstrap-themes/ ) in
Mezzanine?
2. Does anyone know of a Mezzanine theme/template that shows a dropdown
option for website visitor to change theme himself on the fly? (Example:
bootswatch.com site has a
A link for you: https://docs.djangoproject.com/en/dev/topics/auth/default/
The Django documentation is excellent and should be at the top of your
reading list if you intend to work with Mezzanine and/or Cartridge.
On Tue, Sep 23, 2014 at 2:00 PM, vtx...@gmail.com wrote:
Ken
What is django's
Rafael, yes. You are right. The main concept is to add rest_framework to
mezzanine without mixin it with django templates. Currently I'm working on
templates, totally separated where angularjs is at front side with
templates and django on back, where has responsible only for send/get data
and
Yes, of course Rafael's example is useful to create a catch-all URL so
that the front-end can handle URL routing, with real URLS using
html5 pushState (as opposed to '#' based URLs).
Andrzej, perhaps we should start a fresh thread to discuss mezzanine
- rest-framework stuff.
I'll start that
Just moving this discussion to a separate thread from [0]
Stephen, if you (or anyone) have the time to look at my fork on github
and Andrzej Grymkowski's commit [1]: and maybe give a quick opinion
of whether this seems useful to pursue.
Personally, I think for a v1, just making the API
Hi all,
Thanks for your reply.
I will use html/css/js to do this.
Wesley
--
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
At the end of the day, theming a Mezzanine/Django site is a matter of
loading the correct scripts and stylesheets. It seems like
django-bootstrap-themes uses some custom template tags to do so. The demo
website (http://mezzanine.jupo.org/blog/) used to have a theme-switching
widget, perhaps
Here's the commit in the repo for the demo site where I removed the theme
switcher:
https://github.com/stephenmcd/mezzanine.jupo.org/commit/a383f4a83e45698d6c295aa4377f28a1eb8af7a5
You can see how simple it was - it just used javascript to set a cookie for
the user's choice, and those choices
12 matches
Mail list logo
