The Mezzanine-based http://openerparabia.org/ Arabic (RTL) website is now:
http://odooarabia.org/
New brand, new theme, still happily powered by Mezzanine.
--
You received this message because you are subscribed to the Google Groups
"Mezzanine Users" group.
To unsubscribe from this group and
We actually bought the theme back when the site was run by drupal:
http://www.morethanthemes.com/?q=themes/businessclass
Then I manually converted it into a Mezzanine theme, which involved getting
rid of a few dozen nested div's ;)
--
You received this message because you are subscribed to the
Yes.. just when I thought I can take a break from the site, they changed
their brand!
Now we need to rebrand our site too :|
--
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
Django-moderation http://django-moderation.readthedocs.org/en/latest/ can
be consulted for inspiration. I could not integrate it with Mezzanine
easily, but it provides nice features such as showing diffs and
notifications of changes pending approval.
--
You received this message because
Pull request implementing can_move during page moves only:
https://bitbucket.org/stephenmcd/mezzanine/pull-request/64/
- Interface: can_move(request, new_parent)
. Raises a PageMoveException if permission is denied. Does not return
anything.
- Docs included.
- Not called during page creation,
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!
Is there no interest in this feature?
I kinda need it right now. Can we decide one way or the other? The code is
already there. Calling can_move() during page creation is separated into
its own commit.
Pull request: https://bitbucket.org/stephenmcd/mezzanine/pull-request/63/
--
You
Wouldn't a simple regular expression work here?
--
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,
: wrote:
Looks like it's a dupe of
https://github.com/stephenmcd/mezzanine/issues/567 which is open.
On Tue, Jun 3, 2014 at 9:10 AM, Ahmad Khayyat akha...@gmail.com
javascript: wrote:
I was wondering about what happened to issue #816: “add image resizing
feature to media library
(Original thread:
https://groups.google.com/forum/#!topic/mezzanine-users/bIxUJkOIdUM)
I created a new thread to reflect the recent direction, and to solicit
opinions of those interested.
*Objective:*
Support limiting page moves dynamically, the same way can_add(),
can_change(), and
Now that `RICHTEXT_FILTERS` is plural, perhaps this is simply a matter of
shipping a filter in Mezzanine that calls
`mezzanine.core.templatetags.mezzanine_tags.thumbnail`, or at least
documenting this procedure. The thumbnail size (and any other parameters
accepted by `thumbnail`) can be set
On Sun, Jun 1, 2014 at 9:11 AM, Stephen McDonald st...@jupo.org wrote:
If can_move was validated in the admin's model form, and raised a form
validation error, wouldn't the data entered be retained in the browser
without having to ever save anything to the db?
Yes, but how would the user
OK. I took another stab at it:
https://bitbucket.org/stephenmcd/mezzanine/pull-request/63/can_move-permission/
*Pull request description:*
Implement a new can_move dynamic page permission.
Content types can override can_move() to control whether a given page
move in the page tree is permitted.
On Sat, May 31, 2014 at 3:32 AM, Stephen McDonald st...@jupo.org wrote:
I'd guess there's no need to define the alternative parent - it should
always be the previous parent prior to moving.
On Sat, May 31, 2014 at 8:59 AM, Ahmad Khayyat akhay...@gmail.com wrote:
Also, the alternative new
don't see how else the new page can be
placed, except for a brute-force-lookup of a legal position by examining
every existing page as a potential parent.
On Sat, May 31, 2014 at 3:40 AM, Ahmad Khayyat akhay...@gmail.com wrote:
On Sat, May 31, 2014 at 3:32 AM, Stephen McDonald st...@jupo.org wrote
Put another way: creating an instance is not a page move.
On Mon, May 26, 2014 at 4:21 PM, Ahmad Khayyat akhay...@gmail.com wrote:
Right. Yes, they can. But that would be handled by the save method of the
MyPage model (this is what I do in my app). I don't know of a way to handle
Here we go:
https://bitbucket.org/stephenmcd/mezzanine/pull-request/62/
Create and send pre_page_move and post_page_move signals.
Any value returned by any receiver of the pre_page_move signal will abort
the move. The value is considered an error message, and will be displayed.
The first
17 matches
Mail list logo
