You need to know django well in order to understand mezzanine development. On Wednesday, April 29, 2015 at 12:07:42 AM UTC+6, Brandon Keith Biggs wrote: > > Hello, > I am reading the content architecture page and I am wondering where the > .py files are supposed to be saved and how they interact with the HTML > pages? I generally like to type out the examples given and then break them > or change them. > I have no django experience, so should I go through their tutorial before > going into mezzanine, or can I start with mezzanine then go into django if > I wish? > Thanks, > > Brandon Keith Biggs <http://www.brandonkeithbiggs.com/> > On 4/28/2015 7:28 PM, Brandon Keith Biggs wrote: > > Hello, > I think I figured out how to use the editor, you need to click on the html > entry area in order to create HTML, then it makes little fields that are > what you wrote. > Is there a place where I can edit how that add page looks like? I would > like to add a heading at either the text that says: > Content: > > or > > Rich Text Area > > Either that, or make it so when you press tab you are put into the text > editor. > Currently I have to press 3 really weird key commands to move from the > title to the text field. It is really not user friendly for me. (I have to > press capslock+space to exit the forms area, x to move to the menu > checkbox, then shift tab to get into the richtext area.) > Also, is there a key command to switch to the html editor within MCE? > I am having a weird problem that the insert link button is grayed out, so > in order to add a link I have to go into the source and add the link. Does > anyone know what may cause this? > Thanks, > > Brandon Keith Biggs <http://www.brandonkeithbiggs.com/> > On 4/28/2015 5:31 PM, Josh Cartmell wrote: > > Hi Brandon, I don't understand the first question. What was the input > and what would you expect it to produce? > > The widget probably needs to be updated to "django.forms.Textarea" I had > been thinking of something else when I omitted the django. previously. > > On Mon, Apr 27, 2015 at 7:12 PM, Brandon Keith Biggs < > brandonk...@gmail.com <javascript:>> wrote: > >> Hello, >> 2 things: >> 1. setting the allowd markup to everything still produces something like >> <h1>Hello world</h1> >> >> and copying the line: >> RICHTEXT_WIDGET_CLASS = "forms.Textarea" >> >> gives the following error: >> >> ImproperlyConfigured at /admin/pages/richtextpage/9/ >> Could not import the value of settings.RICHTEXT_WIDGET_CLASS: >> forms.Textarea >> Request Method: >> GET >> Request URL: >> http://127.0.0.1:8000/admin/pages/richtextpage/9/ >> Django Version: >> 1.6.11 >> Exception Type: >> ImproperlyConfigured >> Exception Value: >> Could not import the value of settings.RICHTEXT_WIDGET_CLASS: >> forms.Textarea >> >> Thanks, >> >> Brandon Keith Biggs <http://www.brandonkeithbiggs.com/> >> On 4/22/2015 4:46 PM, Josh Cartmell wrote: >> >> Hi Brandon, hopefully the following are helpful answers! >> >> 1. Title + the publishing controls are present across all things that >> inherit from the Displayable class where as the type of content on those >> various models will vary from class to class. Blog Posts have categories >> and content, Rich Text Pages just have content, Links have no content, >> etc... All the admin classes of those models inherit from Displayable so >> they end up all having those things grouped. Besides the technical >> reasons >> I think the consistency is useful and I find it nice to always be able to >> have the publishing controls right there. >> 2. The editor is a WYSIWYG, particularly one called TinyMCE. Here's >> what they have to say about accessibility, >> http://www.tinymce.com/wiki.php/TinyMCE3x:Accessibility, but maybe >> some or all of that isn't working? >> You can change what is used though, for example in your project's >> settings.py file you could put: >> RICHTEXT_WIDGET_CLASS = "forms.Textarea" >> Doing that should get rid of the WYSIWYG and those types of fields >> should just show up as normal HMTL textareas. That would affect any >> admin >> user, not just yourself. >> 3. There isn't anything like that built in, there might be other >> projects that do things like that for Django that you could integrate >> with >> Mezzanine. >> 4. I don't think we have considered Brython but it should be easy to >> integrate any front end technology you want. Right now Mezzanine ships >> with Twitter Bootstrap as a frontend framework and I think most people, >> myself included, are very happy with it. But really, Mezzanine doesn't >> force front end technology on you, it just default to Twitter Bootstrap >> and >> you can change that easily by changing your project's base.html >> Brython does look interesting though so I may have to take a look at >> it at some point! >> 5. Mezzanine does have some user account/profile support. Here are >> the docs, http://mezzanine.jupo.org/docs/user-accounts.html. >> Mezzanine doesn't have any social login support but there are quite a few >> Django apps that do that which you could use to add that functionality >> 6. I tend to use https://www.digitalocean.com/ (VPS) or >> https://www.webfaction.com/ (shared host). I've never used it on a >> cPanel host but you do need ssh access to a host to be able to deploy >> Mezzanine. >> 7. Mezzanine doesn't have plugins in the same sense as Wordpress. >> You can't install anything through Mezzanine's admin interface other than >> possibly adding some Javascript to the content of pages. Here is a list >> of >> modules that have been created for use with Mezzanine, >> http://mezzanine.jupo.org/docs/overview.html#third-party-modules but >> most if not all of them probably require modifying at a minimum your >> projects settings.py file >> >> Here are a few more thoughts: >> >> Mezzanine is Django so anything you can do with Django you can do in >> Mezzanine. That means that when you look for modules you can cast a wider >> net than just looking for things that were specifically made for Mezzanine >> >> The following is my opinion and I'm sure my bias towards Mezzanine will >> show. Mezzanine and Wordpress have fundamentally different philosophies. >> Wordpress is more targeted at end users by making it easy to install >> plugins through the admin interface. I tend to think that with a Wordpress >> site you could get 80% to 90% of the functionality you want with plugins >> but that last 10% may be very difficult. Mezzanine on the other hand >> requires you to either have a developer or know how to code yourself. It >> doesn't try to be all things to all people but does provide a solid core >> feature set and makes it easy for a Django developer to add missing >> functionality. >> >> Hopefully that helps. Welcome to Mezzanine and please keep asking >> questions. Good luck! >> >> On Wed, Apr 22, 2015 at 6:10 AM, Brandon Keith Biggs < >> brandonk...@gmail.com <javascript:>> wrote: >> >>> Hello, >>> After spending 8 months with wordPress, I am throwing my hands up and >>> moving back to my home language python. >>> I saw mezzanine was probably the cms that would give me the least >>> problems, but I have some questions: >>> 1. The edit page screen is really messy and difficult to navigate. I am >>> using a screen reader, so that may be part of it, but why is the publish >>> date stuff right under the title? why is not content right under title? I >>> would like to enter the title, hit tab and enter the page content. Also, >>> why is the body text editor not a multi edit field? The weird thing is that >>> it now is almost unusable... I can't use navigation commands to get into it >>> or out of it, it says "paragraph editable" while arrowing through each line >>> and there is no advantage anywhere for having this. Perhaps it is a wysiwyg >>> editor and that is why I don't see anything good about it. If so, how can I >>> disable the wysiwyg editor for my account? >>> 2. Not being able to write html from within the editor is horrible, I >>> need to fix it. I spent all last night trying to think about how one could >>> change the user permissions on them self, but couldn't come up with >>> anything. Perhaps it has to do with the backend, but it just seems so >>> unlikely it will never happen. >>> 3. Is it possible to add short-codes or code within the editor so I can >>> access variables and or functions that I have created without making a >>> template? >>> 4. Has mezzanine considered distributing brython along with the servers? >>> I can add it, but it would make more sense to have things in brython rather >>> than javascript for a python based product... >>> 5. How is the user account support? I would like to have people connect >>> with Facebook or google and grab info from there to populate the user's >>> fields on their account pages. >>> 6. What hosts are easy to use with mezzanine? I am looking for a new one >>> and would prefer one with CPanel. >>> 7. Are all the plugins there on the front page? Is there a way to get >>> plugins or templates from within the dashboard? This is something that >>> makes wordPress exceptional for quick development. >>> Thank you, >>> >>> -- >>> Brandon Keith Biggs <http://www.brandonkeithbiggs.com/> >>> -- >>> 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 <javascript:>. >>> 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-use...@googlegroups.com <javascript:>. >> 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-use...@googlegroups.com <javascript:>. >> 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-use...@googlegroups.com <javascript:>. > 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.
