2014-03-03 23:33 GMT+01:00 Ross Laird r...@rosslaird.com:
Postgresql authentication can be tricky.
You may need to make changes to your pg_hba.conf file. Like so:
# Database administrative login by Unix domain socket
local all postgrespeer
#
I have the exact same problem. Stephen is there any other solution
different from just copying it to keywords/description or even one custom
text field? (redundant)
However this may slightly increase DB storage, but in terms of performance
it will be a bit faster, not having to join the extra
Wow guys, excellent work you've done here! It's amazing how different the
admin looks with this tweaks. Now, I have a few questions:
1. Would you be interested in using an alternate theme for TinyMCE? I've
been using this for several projects:
To answer your last question Tom, fabric isn't intended to be used for
development, it is intended for production and will take a hosting
environment from blank OS to ready to serve your site automagically.
On Mon, Mar 3, 2014 at 9:25 PM, Stephen McDonald st...@jupo.org wrote:
As for the
I don't actually use Fabric, so I have been a bit hesitant to make
suggestions here. But my guess is that you have one problem and one problem
only, and it just keeps changing how it looks depending on what you do. To
step through a solution to this, I would take Fabric out of the equation
and
Is it possible to validate a form in a page processor?
I know you're able to override the associated form by something like:
*@processor_for('rsvp')*
*def rsvp_form(request, page): *
*form = RsvpForm() # a custom form i created to override the page's
form*
*return {form: form}*
But
Hey Danny,
Check out the example at
https://mezzanine.jupo.org/docs/content-architecture.html#page-processors,
I think it will get you started down the right path and shows how to handle
validation in a processor.
On Tue, Mar 4, 2014 at 9:37 AM, Danny flack flackatt...@gmail.com wrote:
Is it
So first off, I needed to create a custom host-to-order processor for
mezzanine cartridge. I'm using an older version of
mezzanine(1.4.5)/cartridge(0.8.2) and due to the way this project was
initial started, i'm sort of stuck with this (forked/custom) set of code.
I'll update when i've got
Ed, yes to everything - let's use that theme, and please help out with
those regressions you've found.
Thanks a lot!
On Wed, Mar 5, 2014 at 1:40 AM, Eduardo Rivas jerivasmel...@gmail.comwrote:
Wow guys, excellent work you've done here! It's amazing how different the
admin looks with this
Solved my own problem.. Turns out i had an error during the post callback,
causing that section of code to never evaluate.
--
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
There are a few moving parts here, my guess is something failing in the
last of these:
By default in Mezzanine, forms use the fields_for template tag, which is
just a helper for rendering forms:
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/templates/includes/form_fields.html
You can use the SPAM_FILTERS setting to set a list of handlers that
check form and comment submission for spam.
The default uses Akismet (if you have it set up in your site
settings), but you could easily add your own.
For example, I have added the following to my site. I've genericised
this code
12 matches
Mail list logo