Re: CMS 'power' getting started

[Stu]

Well, they do have the DjangoCMS. I agree though, WagtailCMS is vastly 
better, in my opinion.

On Monday, February 21, 2022 at 12:56:45 AM UTC-5 buddie...@gmail.com wrote:

> Django is a web framework not a CMS,  if you want to use a CMS then use 
> wagtail which is a Django based CMS. And Vscode would be sufficient for 
> working with Django. 
>
> If you want many custom features for the CMS then you can use wagtail, as 
> whatever you can do in python you can do in wagtail. 
> On Sunday, 20 February 2022 at 01:01:37 UTC+5:30 mwpow...@gmail.com wrote:
>
>> Hello,
>>
>> Mentioned before, coming at this from a 'power' user standpoint, with 
>> dotnet C++ dev background across platforms, some exposure to Python, 
>> familiar with what django is, and competitors i.e. OrchardCore/CMS.
>>
>> Interested in being CMS productive and eventually also potentially adding 
>> tenants/apps to the overall solution.
>>
>> From the 'power' getting started, what else do I need to know?
>>
>> * Docker might be a possibility eventually, but not to start.
>> * Aiming for a postgres backed environment
>> * Have various Python3 versions installed, the latest is 3.10.2, I think, 
>> just now
>>
>> Also looking for guidance re: project structures, directory layout, 
>> editors perhaps, or is a VS Code sufficient, possibly Eclipse, I don't 
>> know, that sort of thing.
>>
>> From OrchardCore/CMS, somewhat familiar with what/how to treat as 
>> 'source', from the code behind it all, to the content database(s) 
>> themselves, etc, and in potentially multi-author scenarios, with 
>> dev/staging/prod phase lines.
>>
>> Let me know if that makes sense or I can clarify anything getting started.
>>
>> Thanks!
>>
>> Michael W. Powell
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/7a983bd9-2d83-4f60-89da-40ac3b2a3ac8n%40googlegroups.com.

Model Formset Factory

[Stu]

When using a modelform on its own, I see that overriding __init__()
enables the customization of generated forms.

Is it possible to customize each of the modelforms (say changing the
widgets on some of the form fields, adding/removing a field, etc.) in
a modelformset when using modelformset_factory?  The same
customization may be applied to all forms in the formset (based on
requesting user perhaps), or to only some of the forms (based on the
initial modelform data or related data). If so, how would you go about
doing this?

Thanks

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

generate choices list from database

[Stu]

In a similar vein to the OP, I'm trying to populate a choices list for
a form (using newforms) from a database:

nameChoices = Names.objects.filter(initials='AB')
NameSelection.base_fields['names'].widget =
widgets.Select(choices=nameChoices.Name)

However, I am not having much succcess, I get this error:
AttributeError at /names/
'_QuerySet' object has no attribute Name'

Anyone have any ideas?

thanks,

Stu


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---