Re: Activity Reports

[Angelo Dini]

Hello benzkji

We're currently focusing on django CMS 3.5.0 where we have lot of exciting 
new features, thats why the updates fall a bit short.
We're keeping addons updated and release regular bug and security fixes 
from time to time.

The feedback so far hasn't been overwhelming here so we will be looking 
into other ways (like blog posts) to keep the community updated.

Best,
Angelo

On Monday, 11 December 2017 13:33:00 UTC+1, benzkji wrote:
>
> hey Angelo.
>
> I know it's hard to keep things up to date, but I really appreciated your 
> Activity Reports (dont know any other place where I could get more up to 
> date infos on django-cms development).
>
> so, how (and where) is it going - or are you all on IRC and up to date? 
> ;-) 
>
> thx
> ben
>
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/52caad36-86a8-45de-9b2e-fa3a523fb0ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What is the standard travis/codecov configuration?

[Angelo Dini]

Hello Fabrice,

given that the tests there are very basics, we do not weight the codecov 
report as a no go for not merging the PR.
If we see that you submitted a test alongside the PR, it's almost certain 
that it's gonna get merged.

Eventually also ping Paulo again for review and merge.

Cheers
Angelo

On Sunday, 24 September 2017 11:41:40 UTC+2, Fabrice Pardo wrote:
>
> Hi,
>
> After submitting pull request 
> https://github.com/divio/djangocms-snippet/pull/45,
> codecov/patch is complaining about  50% of diff hit (target 65.05%).
>
> The problem is that render method was not covered before patch:
>
> https://codecov.io/gh/divio/djangocms-snippet/src/master/djangocms_snippet/cms_plugins.py#L23
>
> Now the pull request is marked with an infamous red cross, even it is (in 
> my opinion) a not so bad pull request.
>
> Is this red cross not so infamous, or is the travis/codecov configuration 
> too strict?
>
> -- 
> Fabrice
>
>  
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/bc00b7fa-f582-4e7e-a764-e83059e8d2bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Feature request: Template edition in wysiwyg with keditor

[Angelo Dini]

Hello Frédéric

my suggestion would be to have a look at the CKEditor implementation:
https://github.com/divio/djangocms-text-ckeditor

that should get you already pretty far by playing around.

Cheers

On Wednesday, 23 August 2017 08:05:38 UTC+2, Frédéric Roland wrote:
>
> Hi,
>
> I've found a nice js template editor that work using drag and drop.
> I think it would be nice to have a kind of wysiwyg template editor.
>
> Here is the link to their project:
>
> https://github.com/Kademi/keditor
>
> I'm willing to help implement this into Django cms but don't know where to 
> start.
> If someone can advice me and give me directions to how to start it would 
> be a nice help.
>
> Frédéric
>  
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/aa4aabd1-9341-4c1a-bfe8-f4380010916d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: djangocms-history And History

[Angelo Dini]

Hello Brian

The high-level goals for us was to create a simple undo/redo functionality 
for the current session of a user, as this is the most reliably and used 
way of history management.

If you'd like the previous versioning management back (revision) I'd highly 
encourage you to checkout and contribute to:
https://github.com/Blueshoe/djangocms-reversion2

Cheers,
Angelo

On Friday, 30 June 2017 14:33:18 UTC+2, Brian Rutledge wrote:
>
> Thanks, Angelo. Do you have any kind of roadmap or high-level goals for 
> djangocms-history? For example: is reverting to a previously published 
> version of a page something that you have considered, and have ideas about 
> how it would be implemented?
>
> On Thursday, June 29, 2017 at 2:48:34 AM UTC-4, Angelo Dini wrote:
>>
>> Hello Brian
>>
>> we did not stop development, just re-focused now on django CMS 3.5.0.
>>
>> if a Client requests further improvements we will add them to this 
>> repository. This does not mean the community can contribute as well :)
>>
>> Cheers,
>> Angelo
>>
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/efdb0b3c-858a-4a6f-b540-908655d0714c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: djangocms-history And History

[Angelo Dini]

Hello Brian

we did not stop development, just re-focused now on django CMS 3.5.0.

if a Client requests further improvements we will add them to this 
repository. This does not mean the community can contribute as well :)

Cheers,
Angelo

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/33da5981-3040-4e80-be59-2fcfc723065c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Hello John

Thanks for your feedback. Our plan was to develop migration paths to these 
addons as we (Divio) won't actively maintain these addons anymore. If 
someone steps forward and does so, we could talk about commit rights. But 
as it is with open-source, we've no deadline on the migration path. We're 
currently heavily involved into various projects and had so far no client 
who wished to migrate.

I'm currently not aware of any changes that might break cmsplugin-filer but 
that can change of course, also with the introduction of Django 1.11 and/or 
other package updates. The new plugins are though production ready (and 
also used on live instances). The most consuming part of the migration is 
to write a management script to migrate the data and test it.

On Sunday, 4 June 2017 07:11:28 UTC+2, John-Scott wrote:
>
> Hi Angelo,
>
> I may have misunderstood the roadmap for core addons 
> <https://www.django-cms.org/en/blog/2017/02/01/core-addons/>:
>
> Deprecated addons
>> Some older plugins that you may have encountered are now deprecated and 
>> we advise against incorporating them into new projects.
>> These are: 
>>
>>- cmsplugin filer <https://github.com/divio/cmsplugin-filer>
>>
>>
>>- Aldryn Style <https://github.com/aldryn/aldryn-style>
>>
>>
>>- Aldryn Locations <https://github.com/aldryn/aldryn-locations>
>>
>>
>>- Aldryn Snippet <https://github.com/aldryn/aldryn-snippet>
>>
>> We'll be developing migration paths to help users who have these 
>> installed in their projects move to newer, official core addons that 
>> provide the same functionality.
>
>
> I thought that meant *Divio* made the decision to deprecate 
> cmsplugin-filer and would be developing migration paths. I haven't seen any 
> discussion on this list regarding this change, the blog is the only source 
> of details I've seen. It looks like cmsplugin-filer development stopped 
> last fall, but the README has not been updated to warn people away from 
> using it in new projects so it's not clear if it is 'officially' deprecated 
> or not.
>
> Are there any known upcoming changes in django-cms that will break 
> compatibility with cmsplugin-filer? Will pull requests/issues for 
> cmsplugin-filer be ignored going forward? Are the new favored plugins 
> production ready? A quick glance at the djangocms-picture README suggests 
> that beyond needing to do some sort of data migration, users would 
> potentially need to also update templates, settings, etc. Any other known 
> hurdles that will need to be addressed when paving the migration path?
>
> Happy to help test any proposed migration path of course! 
>
> Thanks,
> John-Scott
>
>
> On Thursday, May 25, 2017 at 11:31:41 PM UTC-7, Angelo Dini wrote:
>>
>> Hello John,
>>
>> that is no Problem. It is still on our todo lists but we are a bit 
>> consumed from projects/client work. I can't really give an 
>> estimate/deadline as it's an open-source effort. I'm also very happy if 
>> someone could help or tackle the task.
>> I'd announce it here or via Blog if I'll get to anything.
>>
>> Cheers
>> Angelo
>>
>> On Thursday, 25 May 2017 21:29:29 UTC+2, John-Scott wrote:
>>>
>>> Hi Angelo,
>>>
>>> Just checking back in to see what the latest thinking is on replacing 
>>> the cmsplugin_filer_* plugins as far as deprecation timeline and possible 
>>> paths for migrating to the newer djangocms-* plugins? 
>>>
>>> I haven't followed development on the new plugins closely so apologies 
>>> if this has been answered/solved elsewhere.
>>>
>>> Thanks!
>>> John-Scott
>>>
>>> On Sunday, September 11, 2016 at 11:25:03 PM UTC-7, Angelo Dini wrote:
>>>>
>>>> Hello @john
>>>>
>>>> Yes we want to replace cmsplugin-filer with more specific plugins 
>>>> following the Python Zen "Do one thing, and that good". For that matter we 
>>>> are working on cleanup/improving some existing plugins to replace 
>>>> cmsplugin-filer:
>>>>
>>>> - cmsplugin_filer_file > djangocms-file
>>>> - cmsplugin_filer_folder > djangocms-file
>>>> - cmsplugin_filer_image > djangocms-picture
>>>> - cmsplugin_filer_link > djangocms-link
>>>> - cmsplugin_filer_teaser > djangocms-teaser (though we do not update it 
>>>> for now)
>>>> - cmsplugin_filer_video > djangocms-video
>>>>
>>>

Re: Activity Reports

[Angelo Dini]

Hello John,

that is no Problem. It is still on our todo lists but we are a bit consumed 
from projects/client work. I can't really give an estimate/deadline as it's 
an open-source effort. I'm also very happy if someone could help or tackle 
the task.
I'd announce it here or via Blog if I'll get to anything.

Cheers
Angelo

On Thursday, 25 May 2017 21:29:29 UTC+2, John-Scott wrote:
>
> Hi Angelo,
>
> Just checking back in to see what the latest thinking is on replacing the 
> cmsplugin_filer_* plugins as far as deprecation timeline and possible paths 
> for migrating to the newer djangocms-* plugins? 
>
> I haven't followed development on the new plugins closely so apologies if 
> this has been answered/solved elsewhere.
>
> Thanks!
> John-Scott
>
> On Sunday, September 11, 2016 at 11:25:03 PM UTC-7, Angelo Dini wrote:
>>
>> Hello @john
>>
>> Yes we want to replace cmsplugin-filer with more specific plugins 
>> following the Python Zen "Do one thing, and that good". For that matter we 
>> are working on cleanup/improving some existing plugins to replace 
>> cmsplugin-filer:
>>
>> - cmsplugin_filer_file > djangocms-file
>> - cmsplugin_filer_folder > djangocms-file
>> - cmsplugin_filer_image > djangocms-picture
>> - cmsplugin_filer_link > djangocms-link
>> - cmsplugin_filer_teaser > djangocms-teaser (though we do not update it 
>> for now)
>> - cmsplugin_filer_video > djangocms-video
>>
>> This will mainly help us ship djangocms-installer and the default 
>> installation on Aldryn with good and clean base plugins. Next step will be 
>> to provide facilities to migrate older projects to these new plugins. After 
>> that we will deprecate the old ones (will take some months though). We will 
>> publish blog posts prior to this scenario :)
>>
>>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/4db78f90-bfd8-4193-aba2-2c67eb39f296%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Activity Report 16th of May 2017
-

*News*

   - django CMS loses its head
   https://www.django-cms.org/en/blog/2017/03/14/headless-django-cms/
   - django CMS security updates
   
   https://www.django-cms.org/en/blog/2017/04/26/django-cms-security-updates/
   - Backups on Divio Cloud
   https://www.divio.com/en/blog/backups-on-divio-cloud/
   - What we're working on: improvements to the structure board
   
   
https://www.django-cms.org/en/blog/2017/05/12/improvements-to-the-structure-board/
   
*New Releases:*

   - django CMS  3.4.2 and 3.3.4 
   (Security Release)
   - Aldryn Django  1.8.18.1, 
   1.9.13.1, 1.10.7.1 (Security Release)


   - django CMS Picture  2.0.5
   - django CMS Link  2.1.1
   - django CMS Google Map  
   1.1.0


   - Aldryn Bootstrap 3  1.2.1

*Ongoing Work:*

   - django CMS 3.5.0
   Work for django CMS 3.5.0 continues different fronts:
   - The REST API is being developed 
  
  - django 1.11 efforts on GitHub 
  
  - Split of structure and content mode
  - New features can now be opened to the development branch for 3.5
  
With regards, 

Angelo, on behalf of the core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/6eae67ee-a6d5-47de-bda1-e1f8e94d36b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Aldryn Newsblog and Django 1.10 (or 1.11 LTS) Support

[Angelo Dini]

That is correct, though I'd stick with Django 1.8 (as it's still an LTS) 
though we'll be introducing 1.11 support soonisch.

Best
Angelo

On Tuesday, 2 May 2017 01:29:30 UTC+2, Aubrey Taylor wrote:
>
> I'm here because the maintainers at Aldryn Newsblog keep closing issues 
> requesting support for supported versions of Django.
>
> Django 1.10 support ends this december, 1.9 ended in April.
>
> The problem is that Aldryn Newsblog pins to (no greater than) 1.9.x in the 
> latest version which means its only compatible with an unsupported version 
> of Django. 
>
> To quote the Aldryn Newsblog docs:
>
> > Divio is committed to Aldryn News & Blog as a high-quality application 
> that helps set standards for others in the Aldryn/django CMS ecosystem, and 
> as a healthy open source project.
>
> Only supporting a now defunct version of Django seems to contradict this 
> statement a bit. And I can only imagine users at Divio are unaware that 
> they are likely running on an-unsupported version of Django if they are 
> also using Aldryn Newsblog. 
>
> My question is, what is the ETA (if any) for a version of Aldryn newsblog 
> that at least supports Django 1.10 (though it really should aim at Django 
> 1.11 support since that is scheduled for LTS).
>
> Thanks for your time and responses. 
>
> (PS. Issues at the Aldryn Newsblog repo have been opened and subsequently 
> closed. The maintainers directed the OP here, but I could not find a 
> matching topic).
>
> Best Regards,
> Aubrey Taylor
>
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/4b38a4c2-6090-4714-811c-6d6ca58fcdfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: The handling of inherited placeholders in edit mode

[Angelo Dini]

I agree, we should add an icon or indication that it is an inherited 
placeholder. 

there is also already a ticket to track 
it: https://github.com/divio/django-cms/issues/5037

Best
Angelo

On Tuesday, 2 May 2017 14:56:57 UTC+2, Gregor Kopka wrote:
>
> I would like to chime on in this:
>
> {% placeholder "foo" inherit %} is currently extremely confusing as 
> visible content simply vanishes from the page when entering edit mode.
>
> This is somewhat livable with in structure mode (a note that the 
> placeholder inherits from the parent would be helpful though), but in 
> content mode this just leads to calls from users asking to revert the 
> mistake they just made (as it makes them think that they just deleted stuff 
> by accident).
>
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/ad49505a-1e19-4ff6-96fb-545ad8142c71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Aldryn Newsblog and Django 1.10 (or 1.11 LTS) Support

[Angelo Dini]

Hello Aubrey

It is indeed true that we have lacked support for Aldryn News & Blog due to 
time restraints on our hand. We are heavily involved into Divio Cloud and 
have recently upgraded the Core Addons to our latest standards 
(https://www.django-cms.org/en/blog/2017/02/01/core-addons/). We are also 
currently working on Django 1.11 support for django CMS 3.4.x 
(https://github.com/divio/django-cms/pull/5932)

I'm sorry that progress on the essential addons (Newsblog, People, FAQ, 
Jobs, Events) are lacking and we most likely will not update them until we 
have introduced 1.11 support. After that we want to upgrade the core addons 
and switch after that our focus to the essential addons.

You are welcome to propose pull request and you can always ping be 
(FinalAngel) to have a second look or ask the corresponding people for help.

Thank You
Angelo


On Tuesday, 2 May 2017 01:29:30 UTC+2, Aubrey Taylor wrote:
>
> I'm here because the maintainers at Aldryn Newsblog keep closing issues 
> requesting support for supported versions of Django.
>
> Django 1.10 support ends this december, 1.9 ended in April.
>
> The problem is that Aldryn Newsblog pins to (no greater than) 1.9.x in the 
> latest version which means its only compatible with an unsupported version 
> of Django. 
>
> To quote the Aldryn Newsblog docs:
>
> > Divio is committed to Aldryn News & Blog as a high-quality application 
> that helps set standards for others in the Aldryn/django CMS ecosystem, and 
> as a healthy open source project.
>
> Only supporting a now defunct version of Django seems to contradict this 
> statement a bit. And I can only imagine users at Divio are unaware that 
> they are likely running on an-unsupported version of Django if they are 
> also using Aldryn Newsblog. 
>
> My question is, what is the ETA (if any) for a version of Aldryn newsblog 
> that at least supports Django 1.10 (though it really should aim at Django 
> 1.11 support since that is scheduled for LTS).
>
> Thanks for your time and responses. 
>
> (PS. Issues at the Aldryn Newsblog repo have been opened and subsequently 
> closed. The maintainers directed the OP here, but I could not find a 
> matching topic).
>
> Best Regards,
> Aubrey Taylor
>
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/02d05710-4d87-4e25-a0f7-80f717322bb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Activity Report 14th of March 2017
-

*News*

   - PyCon Namibia 2017 - a personal view
   https://www.divio.com/en/blog/pycon-namibia-2017/
   - Django deployment made as easy as ABC (and PHP)
   
   https://www.divio.com/en/blog/django-deployment-made-as-easy-as-abc-and-php/

*New Releases:*

   - Aldryn Django  1.10.5.0 with 
   Django 1.10 support in alpha channel
   - Aldryn django CMS  3.4.2.5


   - django CMS Style  2.0.2
   - django CMS Filer  1.2.7
   - django CMS Attributes Field 
    0.2.0


   - Aldryn SSO  1.1.14
   - Aldryn Bootstrap 3  1.2.1
   - Aldryn Sites  0.5.6
   - Aldryn Boilerplates  
   0.7.5

*Ongoing Work:*

   - django CMS 3.5.0
   Work for django CMS 3.5.0 continues different fronts:
   - The REST API is being developed 
  
  
With regards, 

Angelo, on behalf of the core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/22a109c0-c56d-4fe7-8228-16dbde749d77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.11 LTS Support

[Angelo Dini]

Hello Nick

we have a patch for 3.4 supporting Django 1.11 on our radar, this also 
means 3.5 will support it (or patched thereafter).
Though we cannot say yet how smooth the update might be, that all depends 
on the upcoming Release Candidates.

Also when we are ready depends on testing, community contributions and our 
own available time. So you're welcome to help out.

Cheers
Angelo


On Tuesday, 21 February 2017 17:52:35 UTC+1, Nick Catalano wrote:
>
> Hi-
>
> We want to use the latest version of DjangoCMS for our project, but far 
> more important to us is we never want to run our website on a non-supported 
> version of Django that isn't receiving security patches. The next LTS 
> version of Django is 1.11, while 1.10 ends all support in December.
>
> Will 3.4 (your LTS version) support 1.11 by December, when Django 1.10 
> ends support? Alternatively, will DjangoCMS 3.5 be released before 
> December, support 1.11, and be a straightforward upgrade from 3.4?
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/fa54998a-0ddf-490a-bbd0-283fd85b9e12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Activity Report 6th of February 2017
-

*News*

   - The very first django CMS Day in review
   https://www.django-cms.org/en/blog/2016/10/04/django-cms-day-review/
   - Maintenance versions 3.4.1 and 3.3.3 released
   
   
https://www.django-cms.org/en/blog/2016/10/05/maintenance-versions-3-4-1-and-3-3-3-released/
   - django CMS 3.4.2 released
   https://www.django-cms.org/en/blog/2017/01/25/django-cms-3-4-2-released/
   - Core Addons
   https://www.django-cms.org/en/blog/2017/02/01/core-addons/
   - Back in time with django CMS
   
   https://www.django-cms.org/en/blog/2017/02/03/back-in-time-with-django-cms/
   - Docker goes native
   https://www.divio.com/en/blog/docker-goes-native/
   
*New Releases:*

   - django CMS  3.3.3
   - django CMS  3.4.2


   - django CMS History  0.3.0 
   (new)
   - django CMS Link  2.1.0
   - django CMS Google Map  
   1.0.2


   - Aldryn Bootstrap  1.2.0

*Ongoing Work:*

   - django CMS 3.5.0
   Work for django CMS 3.5.0 continues different fronts:
   - The REST API is being developed 
  
  - Further adaptions/fixes to 3.4.x if necessary
  
With regards, 

Angelo, on behalf of the core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/b73509b0-ee2f-402c-8805-a5aa1add27a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Add more style elements

[Angelo Dini]

Hallo Micheal, which style plugin are you using?
The officially supported djangocms-style 
(https://github.com/divio/djangocms-style) has a setting where you can 
override the defaults:

DJANGOCMS_STYLE_TAGS = ['div', 'article', 'section', 'header', 'footer',
'h1', 'h2', 'h3', 'h4', 'h5', 'h6']


It does not make sense to add all html tags as that would confuse the 
end-user. Just simple adapt the setting to your needs.

Cheers
Angelo

On Thursday, 12 January 2017 17:22:32 UTC+1, Michael Schlegel wrote:
>
> Is there a plan to add more semantic HTML5 elements to the "style" plugin? 
> My question is related to the list of HTML5 elements which are listed here: 
> http://www.w3schools.com/html/html5_semantic_elements.asp. Some of the 
> them are already part of the "style" plugin but by far not all of them. 
>
> Thanks & regards
>
> Michael 
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/a24b01ee-701a-4651-bb59-435f98c9a0b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: django

[Angelo Dini]

Hello, please 
checkout http://docs.django-cms.org/en/stable/introduction/install.html

On Sunday, 1 January 2017 17:11:12 UTC+1, Manish Jain wrote:
>
> Hello, please i am new in django so please tell me fresh installation 
> step. 
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/22113605-2b1b-4192-9bb5-ad0677e3d8a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Structure vs. Content mode - front-end editing needs better UX

[Angelo Dini]

Hello Peter

thank you very much for the wireframe. My experience with a toolbar 
restricting the width of the viewport and especially the websites width is 
in general bad. This also lead us to reconsider the sidebar and overlap it 
over the content. It's not an option that I'd consider but I can place it 
in the board meeting.

I'd rather have it on the bottom of the page spanning fullwidth, also 
considering that a structure can have many nested level and width will be a 
problem. We could eventually implement switches, such as the developer 
tools offer.

I like the idea of the toolbox but might feel more comfortable adding that 
to the content itself with hover indications or so, but we'd need some UX 
tests for that.

Cheers
Angelo

On Wednesday, 21 December 2016 21:10:34 UTC+1, Peter Bittner wrote:
>
> Hi Angelo,
>
> I've made a quick wireframe, see attached. It's available for public 
> editing at https://wireframe.cc/IBlaDw
>
> A CMS sidebar can solve the issue of the toolbar occupying "too much" 
> screen real estate. It can easily collapse or slide out (as the toolbar did 
> in django CMS 2.4, by the way!), and users will feel alright. On large 
> desktop screens the default placement on the right (or left) comes natural 
> as most screens are much wider than high, nowadays. Containers inside the 
> sidebar can have accordions to accommodate several tools. And no toolbar 
> means 100% of vertical space remains available. The Admin panel can still 
> float in from the left if needed.
>
> The toolbox offers all plugins (in a context sensitive way) to drag and 
> drop them onto the page. The structure below allows for ultimate control 
> and fine-tuning. With the toolbox and the structure view both available at 
> the same time there is no context-switching needed, no losing of context 
> happens while working on the page content. Of course, the sidebar could 
> optionally detach (into a separate window) or be rearranged or moved to one 
> of the other 3 edges of the browser window.
>
> Peter
>
>
> 21 Dec 2016 11:22:51 UTC+1 Angelo Dini wrote:
>>
>> Hello Peter
>>
>> yes, this is why we need to enhance the content mode to enable simple 
>> addition and restructuring of content. Though we will still have the issue 
>> of losing context.
>>
>> I'm very open here to recommendations / UX ideas or sample screenshots of 
>> a possible solution.
>>
>> The technical requirements there are still that the modes are split 
>> apart. We can link them with a new "developers view" mode or whatever we 
>> wanna call it to mimic the developer tools.
>> I find myself more splitting the developers tools from the actual window, 
>> using 2 windows. That might also be worth having a look at.
>>
>> Cheers
>> Angelo
>>
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/497dd39c-bf2c-4483-82b4-5c657afe676a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Structure vs. Content mode - front-end editing needs better UX

[Angelo Dini]

Hello Peter

yes, this is why we need to enhance the content mode to enable simple 
addition and restructuring of content. Though we will still have the issue 
of losing context.

I'm very open here to recommendations / UX ideas or sample screenshots of a 
possible solution.

The technical requirements there are still that the modes are split apart. 
We can link them with a new "developers view" mode or whatever we wanna 
call it to mimic the developer tools.
I find myself more splitting the developers tools from the actual window, 
using 2 windows. That might also be worth having a look at.

Cheers
Angelo

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/a989f53e-f171-4623-9668-3d7ce069bf94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Structure vs. Content mode - front-end editing needs better UX

[Angelo Dini]

Hallo Peter

thanks for the feedback and proposition. One trick that helps is switching 
context via SHIFT + Space, that will highlight the current _hovered_ 
element. The main reasons for two modes are:
- Headless mode, this will be added in the future and will disable content 
entirely and allows the CMS to be run headlessly for frontend frameworks or 
applications
- Permissions, some people should only be able to "edit" content vs 
"restructuring", this way we create separate roles for the CMS
- Legacy, as we had to support IE6/7 back in the days we had limitations on 
what was possible through frontend

We hear you and would like to improve the content mode itself to allow for 
simple restructuring or adding content "lite" version. So people could 
easily add images, text or so inline. The structure mode is intended for 
advanced user that are free to do whatever they want. Even with your 
suggestion with an inspector, the experience would still be reserved to 
experienced users. In addition to that we do not want to limit the view 
space, the toolbar is sometimes already be considered as "distractor" when 
editing content.

These are my thoughts :)

Cheers
Angelo

On Sunday, 18 December 2016 17:14:43 UTC+1, Peter Bittner wrote:
>
> Hi all,
>
> I'd like to ask about the reasons for having a Structure _*versus*_ 
> Content mode switch. We do front-end editing to avoid losing context with 
> what we want to change. Now, when we switch to structure mode all the 
> content is hidden---and we lose context. I've seen this impression 
> confirmed with unskilled, untrained, first-time, and elderly users.
>
> Structure information is good for precise editing, it should be supportive 
> information though. The real state of the page should stay visible, so the 
> context remains established.
>
> How about doing editing as with Firebug (Inspect Element, etc. in your web 
> browser)? With a structure panel open on one side of web page (and a plugin 
> panel / toolbox open on another side of the web page) we could have all the 
> information we need for editing visible at the same time. When hovering 
> over a plugin or placeholder on either the web page or the structure panel 
> the corresponding element on the other could be highlighted. Just like web 
> developers love it when analyzing a web site.
>
> Any thoughts on this?
> Peter
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/b9b272d3-db13-4934-a3cb-542e2147ffa2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Menu tree vs. Path tree

[Angelo Dini]

Hello Brian

the intended goal of Multiple Menu support is to avoid creating menu 
entries with reverse id's to for example render /footer/impressum, 
/footer/about...
you will be able to create additional menus /besides "Main Navigation" that 
than can be used using a template tag, for example {% show_partial_menu 0 
100 100 100 "footer_navigation" %}

this will solve the issue for extra menus. It will however not solve the 
issue in a current tree rendering. So in your case:


   - section-1
  - subsection-1
 - page-1
 - page-2
  - subsection-2
 - page-3
  
Section 1 would be a new "Multiple Menu" node "Section 1". It's url will 
_not_ be rendered when parsing the menu. The path will also not be 
/section-1/subsection-1/page-2 anymore as it acts from its root: 
subsection-1/page-2. "section 1" will then only be a label. Ofc. you can 
still have naming/slug collisions if another menu defines that already.

Hope that helps.

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/1c0a6b68-810b-46d9-825c-fba8853ad613%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Activity Report 28th of November 2016
-

*News*

   - The future’s looking more Pythonic than ever
   
   https://www.divio.com/en/blog/the-futures-looking-more-pythonic-than-ever/
   - Meet us at PyCon DE 2016
   https://www.divio.com/en/blog/meet-us-at-pycon-de-2016/

*New Releases:*

   - django CMS Text CKEditor 
    3.3.1
   - django CMS Admin Style 
1.2.6


   - django CMS Link  2.0.3
   - django CMS Picture  2.0.4
   - django CMS Style  2.0.1
   - django CMS Snippet  1.9.2
   - django CMS File  2.0.2
   - django CMS Google Map 
1.0.1
   - django CMS Video  2.0.3
   - django CMS Audio  1.0.2


   - django CMS Attributes Field 
    0.1.2
   - django CMS Boilerplate Webpack 
    1.1.1
   - django CMS Boilerplate Bootstrap 3 
    4.1.1


   - Aldryn Events  1.1.7
   - Aldryn django CMS 
3.2.5.14
   
*Ongoing Work:*

   - django CMS 3.5.0
   Work for django CMS 3.5.0 continues different fronts:
  - The REST API is being developed 
  
  - A separate package for revisions undo/redo is on its way
  - Further adaptions/fixes to 3.4.x if necessary
   
With regards, 

Angelo, on behalf of the core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/7c213409-fcf4-411d-b97c-bf6016bc2e38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Changing plugin settings results in missing migrations

[Angelo Dini]

I'll be porting the fix to the other core addons, will try to release them 
around early next week.

On Wednesday, 16 November 2016 20:20:12 UTC+1, Brian Rutledge wrote:
>
> I posted this issue to djangocms-style 
> , but it seems to me 
> that it affects multiple plugins, so I'm re-posting the description here.
>
> I just upgraded to 2.0.0, and discovered that setting 
> DJANGOCMS_STYLE_CHOICES and DJANGOCMS_STYLE_TEMPLATES results in changing 
> the choices for class_name 
> 
>  
> and template 
> ,
>  
> which necessitates new migrations. It looks any djangocms plugin that uses 
> this pattern (-link, -picture, etc.) will display this behavior. I am not 
> an expert on migrations, so it's not clear to me what problems it might 
> cause, but it make me nervous about future conflicts, and having migrations 
> outside of source control.
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/b2c1cd1b-407a-457e-b8b2-8bd5f74f93fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Changing plugin settings results in missing migrations

[Angelo Dini]

Thanks for the report here Brian and John,

as soon as I'm aware of the proper solution to this problem, I'll make sure 
it gets added to the checklist and in the near future to our addon best 
practices. Any advice is welcome.

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/3a63cd06-5974-424a-a3e0-ea619108774a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Hello Brian

I'd like to release it today, though that depends on testing. There are 
some issues still in the configuration.

On Monday, 14 November 2016 15:10:46 UTC+1, Brian Rutledge wrote:
>
> Is there an ETA for djangocms-style 2.0?
>
> On Monday, October 24, 2016 at 11:23:12 AM UTC-4, Angelo Dini wrote:
>>
>> Activity Report 24th of October 2016
>> -
>>
>> *News*
>>
>>- Maintenance versions 3.4.1 and 3.3.3 released
>>
>>
>> https://www.django-cms.org/en/blog/2016/10/05/maintenance-versions-3-4-1-and-3-3-3-released/
>>- The very first django CMS Day in review
>>https://www.django-cms.org/en/blog/2016/10/04/django-cms-day-review/
>>- django CMS at PyCon UK 2016
>>https://www.django-cms.org/en/blog/2016/09/22/pycon-uk-2016/
>>- Now available: django CMS 3.4, with Long Term Support
>>
>>
>> https://www.django-cms.org/en/blog/2016/09/15/released-django-cms-3-4-long-term-support/
>>
>> *New Releases:*
>>
>>- django CMS <http://django-cms.org/> 3.4.1 LTS
>>- django CMS <http://django-cms.org/> 3.3.3
>>- 
>>
>> https://www.django-cms.org/en/blog/2016/09/15/released-django-cms-3-4-long-term-support/
>>
>>
>>- django CMS Text CKEditor 
>><https://github.com/divio/djangocms-text-ckeditor> 3.3.0
>>- django CMS Admin Style 
>><https://github.com/divio/djangocms-admin-style> 1.2.5
>>- django CMS Picture <https://github.com/divio/djangocms-picture>
>> 2.0.2
>>- django CMS File <https://github.com/divio/djangocms-file> 2.0.1
>>- django CMS Video <https://github.com/divio/djangocms-video> 2.0.2
>>- django CMS Link <https://github.com/divio/djangocms-link> 2.0.1
>>
>> *Ongoing Work:*
>>
>>- Addons
>>The remaining djangocms-style and djangocms-googlemap changes will be 
>>released soon.
>>- django CMS 3.5.0
>>Work for django CMS 3.5.0 has begun on different fronts:
>>   - The REST API is being developed 
>>   <https://github.com/divio/djangocms-rest-api>
>>   - A separate package for revisions undo/redo is on its way
>>   - Further adaptions/fixes to 3.4.x if necessary
>>
>> With regards, 
>>
>> Angelo, on behalf of the core team
>>
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/5e518c07-d17d-4bd0-9fb3-a173fc1f8eb5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: hide DjangoCMS version in toolbar for non-admin users

[Angelo Dini]

+ 1

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/f28dcec6-ad57-46ea-a691-b88c78cd2be1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Activity Report 24th of October 2016
-

*News*

   - Maintenance versions 3.4.1 and 3.3.3 released
   
   
https://www.django-cms.org/en/blog/2016/10/05/maintenance-versions-3-4-1-and-3-3-3-released/
   - The very first django CMS Day in review
   https://www.django-cms.org/en/blog/2016/10/04/django-cms-day-review/
   - django CMS at PyCon UK 2016
   https://www.django-cms.org/en/blog/2016/09/22/pycon-uk-2016/
   - Now available: django CMS 3.4, with Long Term Support
   
   
https://www.django-cms.org/en/blog/2016/09/15/released-django-cms-3-4-long-term-support/

*New Releases:*

   - django CMS  3.4.1 LTS
   - django CMS  3.3.3
   - 
   
https://www.django-cms.org/en/blog/2016/09/15/released-django-cms-3-4-long-term-support/
   

   - django CMS Text CKEditor 
    3.3.0
   - django CMS Admin Style  
   1.2.5
   - django CMS Picture  2.0.2
   - django CMS File  2.0.1
   - django CMS Video  2.0.2
   - django CMS Link  2.0.1

*Ongoing Work:*

   - Addons
   The remaining djangocms-style and djangocms-googlemap changes will be 
   released soon.
   - django CMS 3.5.0
   Work for django CMS 3.5.0 has begun on different fronts:
  - The REST API is being developed 
  
  - A separate package for revisions undo/redo is on its way
  - Further adaptions/fixes to 3.4.x if necessary
   
With regards, 

Angelo, on behalf of the core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/d6e8f33c-272f-455a-9801-5ea56d7c9bf8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Code review checklist

[Angelo Dini]

Hello @John

We do have some sort of checklist though it's mostly shared verbally 
between the core developers.
I think it would make sense to eventually further 
expand http://docs.django-cms.org/en/release-3.4.x/contributing/code.html

any other opinion?

Cheers
Angelo

On Saturday, 22 October 2016 06:08:08 UTC+2, John-Scott wrote:
>
> Is there any sort of code review checklist used internally by the core 
> developers? Something that could be referenced by reviewers before 
> approving changes, e.g. 'If this change modifies a public API call 
> signature, be sure to clearly document the impact/follow the deprecation 
> policy/etc'.
>
> It's easy to quickly scan a pull request and give a :thumbsup: but it may 
> not be immediately apparent to the reviewer that there are gotchas to 
> consider. I accept that we'll always run into unanticipated issues (such is 
> life!), but I'd like to see these 'lessons learned the hard way' turned 
> into a formal checklist so reviewers will be prompted to look for these 
> types of issues going forward.
>
> Concretely, I've been bitten several times over the years by backwards 
> incompatible changes that were not clearly identified in the release 
> notes/history/changelog of django-cms and related plugins. 
>
> A recent example is described in this djangocms-link issue 
>  and pull request 
> . In this case, the 
> default template changed paths and the context variables also changed. 
> However, the changelog only said "* Cleaned up file structure". It wasn't 
> clear at all from this that this impacted those of us who had customized 
> the default template. Users are left to either experience the bug in 
> production after what was assumed to be an innocent upgrade, or they have 
> to be extremely thorough and review every git commit before upgrading.
>
> A checklist or some such document could be helpful in bringing structure 
> to how future changes are evaluated.
>
> Thoughts?
>
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/f4d216c2-bf58-45ff-b006-d00b2c05dfbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Hello @john

Yes we want to replace cmsplugin-filer with more specific plugins following 
the Python Zen "Do one thing, and that good". For that matter we are 
working on cleanup/improving some existing plugins to replace 
cmsplugin-filer:

- cmsplugin_filer_file > djangocms-file
- cmsplugin_filer_folder > djangocms-file
- cmsplugin_filer_image > djangocms-picture
- cmsplugin_filer_link > djangocms-link
- cmsplugin_filer_teaser > djangocms-teaser (though we do not update it for 
now)
- cmsplugin_filer_video > djangocms-video

This will mainly help us ship djangocms-installer and the default 
installation on Aldryn with good and clean base plugins. Next step will be 
to provide facilities to migrate older projects to these new plugins. After 
that we will deprecate the old ones (will take some months though). We will 
publish blog posts prior to this scenario :)

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/22f130b2-23e7-44f2-b940-cea8bc3dc58e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Activity Report 9th of September 2016
-

*News*

   - django CMS CKEditor 3.1.0 / 3.2.0
   
   https://www.django-cms.org/en/blog/2016/08/19/djangocms-text-ckeditor-3-1-0/
   - We are saying goodbye to our GitHub wiki
   
   
https://www.django-cms.org/en/blog/2016/08/25/we-are-saying-goodbye-to-our-github-wiki/
   - RC1 Release of django CMS 3.4 LTS
   
   https://www.django-cms.org/en/blog/2016/08/30/rc1-release-of-django-cms-3-4/
   - Expert Hours: the Doctor is In
   https://www.divio.com/en/blog/expert-hours-the-doctor-is-in/
   - Scaling the peaks of Hacker News
   https://www.divio.com/en/blog/scaling-the-peaks-of-hacker-news/
   
*New Releases:*

   - django CMS  3.4.0 RC1
   
   https://www.django-cms.org/en/blog/2016/08/30/rc1-release-of-django-cms-3-4/


   - django Filer  1.2.5
   - django CMS Snippet  1.9.1
   - django CMS Picture  2.0.0
   - django CMS Audio  1.0.1
   - django CMS Video  2.0.1
   
   - Aldryn News & Blog  1.3.0
   - Aldryn People  1.2.2
   - Aldryn Jobs  1.2.2
   - Aldryn Events  1.1.6
   - Aldryn Forms  2.1.3
   - Aldryn Bootstrap  1.1.2
   - CMSPlugin Filer  1.1.3


*Ongoing Work:*

   - Addons
   We are continuing work on djangocms-file, djangocms-link, 
   djangocms-googlemap and djangocms-style to have a set of core plugins that 
   work well with a nice and consistent user interface.
   - django CMS 3.4.0
   Our main focus is the release if the first LTS version of django CMS, 
   3.4.0. We are aiming for a release next week if there are no major issues 
   found blocking the release.

With regards, 

Angelo, on behalf of the core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/b5b4005c-6999-4728-b7e4-f2b3718a17d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: django-classy-tags and django-sekizai update

[Angelo Dini]

Awesome job man!

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/c2405bf9-b057-4152-a608-d6a07dba8f4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Activity Report 18th of August 2016
-

*News*

   - Aldryn, the security-minded web service
   https://www.divio.com/en/blog/security-on-aldryn/
   - What we did at EuroPython
   https://www.django-cms.org/en/blog/2016/07/28/what-we-did-at-europython/
   - Part 9: Creating Your First django CMS Plugin
   
   
https://www.django-cms.org/en/blog/2016/07/26/how-to-build-a-website-and-blog-with-django-cms-without-knowing-python-django-pt-9/
   
*New Releases:*

   - django CMS  3.3.2
   
   
https://www.django-cms.org/en/blog/2016/08/12/maintenance-version-3-3-2-of-django-cms-released/
   

   - django CMS Text CKEditor 
    2.9.5
   - django CMS Audio  0.1.2
   - Aldryn Common  1.0.4
   - Aldryn Jobs  1.2.1
   - Aldryn News & Blog  1.2.4
   - Aldryn Django  1.9.8.1
   - Aldryn Django  1.8.14.2

*Ongoing Work:*

   - Revision
   We have decided to remove revision from the 3.4 LTS release to later 
   re-introduce it through a separate addon. Revision has caused several 
   problems in the past, breaking pages rendering them unusable.
   - Testing
   We are soon going to release the first RC of django CMS 3.4. We ask the 
   community to help testing to move forward to a swift release.
   - Addons
   We are working on several addons simultaneously to get them ready for 
   3.4. This mostly includes cleanups and standardisation between the setups.

With regards, 

Angelo, on behalf of the core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/29611626-d6b3-4635-a7c5-ce3230ac4365%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publish workflow for all apps

[Angelo Dini]

Hello benzkji 

Yes we thought already about it and it seems a bit more complicated than 
expected. It requires some major refactors of several CMS components to 
make this work. Eventually Paulo or Martin could lay out the problematics 
in more detail.

Cheers
Angelo

On Saturday, 13 August 2016 08:37:30 UTC+2, benzkji wrote:
>
> Hi all
>
> Publishing content with django-cms is super easy, and the draft/live 
> concept is great. But, have you ever thought about applying that concept to 
> external apps/models too, ie, generalize the concept and make it available 
> to all apps?
>
> It's just...more than one time, I felt a bit awkward when explaining like 
> "but with the news/jobs/whatever, the changes are online immediatly" to a 
> client (my models normally just have a "published" BooleanField).
>
> Any thoughts on this (I already posted this to google, but might reach 
> another audience here...)?
>
> Best
> Ben
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/fda99761-200b-4b27-87ec-b56071118ae4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Feature Request: Concurrent Editing

[Angelo Dini]

Extract from the initial Pull Request and Issue:

It would be really great if we can provide visual feedback on who is 
viewing or editing the current page. The locking/unlocking mechanics could 
be introduced in a later step, with more discussions and feedback 
beforehand. We discussed the visual feedback within the team and would 
suggest the following UI/UX strategy:
[image: image] 
[image:
 
image] 



The image on the left shows the UI element added when the feature is 
enabled (via setting). The right image is showing the hover state. Once you 
click on the icon:


[image: image] 
[image:
 
image] 



A popup will open as shown on the left. The list will show 2 states ordered 
by:

   - Users editing the page
   - Users viewing the page

If there are no editors, the icon stays grey. The color of the icon only 
changes to yellow once there is someone editing in any language of the 
current page. Always show the editors of your language first, and then 
other languages etc. As there can be multiple same users editing (for lack 
of account management) the entry representing "you" is specifically marked.

When hovering over an entry as shown on the right, we show an additional 
tooltip on who it is (IP based) and since when he's editing the page. 
Clicking on the entry redirects to the user in the admin.

It's then very important to find the right balance using signals as @yakky 
 mentioned. So that someone doesn't stay as "in 
edit" forever.

For the future this can be enhanced with user locking or a simple messaging 
system to notify each other. One step at-a-time. WDYT?

Original Pull Request:
https://github.com/divio/django-cms/pull/5234

Related Issue:
https://github.com/divio/django-cms/issues/3774

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/03597ee8-8b3b-4e51-8246-e3d3e6f5cdd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: History Diff feature

[Angelo Dini]

That looks great, indeed the history would be enhanced with such 
functionality.
Did you also had a chance while working on that feature to address the 
basic problems of the history feature?

Cheers
Angelo

On Wednesday, 20 July 2016 18:40:58 UTC+2, Martin Owens wrote:
>
> The inkscape project has worked on a diff feature of django-cms, it's 
> currently a separate app in our repository, but I'm brining it to 
> django-cms project's attention to see if it's useful for other users.
>
>
> See screenshots for examples. It follows the wikia diff form pattern and 
> uses reversion with diff_match_patch to produce colour diff output.
>
>
> Screenshots can be found on this closed bug report: 
> https://github.com/divio/django-cms/issues/5556
>
>
>
>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/de8d0393-3370-44a1-870b-31e464eddb82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Activity Reports

[Angelo Dini]

Activity Report 20th of July 2016
-

*News*

   - django CMS Day in Florence
   https://www.django-cms.org/en/blog/2016/07/18/django-cms-day-in-florence/
   - Really fast Django sites with Aldryn
   https://www.divio.com/en/blog/really-fast-django-sites-with-aldryn/
   - As fast as possible with django CMS
   
   
https://www.django-cms.org/en/blog/2016/07/04/as-fast-as-possible-with-django-cms/
   
*New Releases:*

   - django CMS  3.3.1
   
   
https://www.django-cms.org/en/blog/2016/07/13/maintenance-version-3-3-1-released/


   - Aldryn Bootstrap 3  1.1.1
   - Aldryn Events  1.1.5
   - Aldryn FAQ  1.2.1
   - CMSPlugin Filer  1.1.2
   - django CMS Link  1.8.2
   - django CMS Boilerplate Webpack 
    1.0.1

*Ongoing Work:*

   - Editing Experience
   We are heading towards the finish line for better preview of content 
   within djangocms-text-ckeditor.
   Please help out testing on the current progress 
   https://github.com/divio/djangocms-text-ckeditor/pull/333.
   - Speed Improvements
   We have made again further progress on speed improvements towards the 
   usage of the structure mode and the create/save plugin actions.
   - Alias Plugin
   Progress has been slow due to our focus on the editing experience and 
   speed improvements.
   Therefore we will be fixing only issues related to user-braking actions 
   (such as the recursion problems).

With regards, 

Angelo, on behalf of the core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/e85fa329-10c2-4915-9846-184d30410920%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Activity Reports

[Angelo Dini]

Dear django CMS developers, 

We want to keep everyone updated better about work that's going on in the 
project, so we are going to try posting regular bulletins summarising work. 
These bulletins will cover django CMS itself, and also related projects in 
the ecosystem.


With regards, 
Angelo, on behalf ofthe core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/48e10fef-4f89-4099-9ac3-d6125e0bb8f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Activity report 7th July 2016

[Angelo Dini]

Dear django CMS developers, 

We want to keep everyone updated better about work that's going on in the 
project, so we are going to try posting weekly bulletins summarising work. 

These bulletins will cover django CMS itself, and also related projects in 
the ecosystem.

What we've done the last two weeks: 

   - Released: aldryn-newsblog 1.2.3
   - Released: aldryn-faq 1.2.0
   - Released: aldryn-locations 1.0.1
   - Released: django Filer 1.2.2
   - Released: djangocms-admin-style 1.2.3
   - Released: djangocms-googlemap 0.5.1
   - Released: djangocms-attributes-field 0.0.5
   - Fixed: issues related to djangocms-attributes-field

Goals for next week: 

   - 
   - Editing Experience
  - We are looking into ways on how to preview content correctly inside 
  the CKEditor instead of static images, we are aiming for a solution until 
  the end of next week
  - The speed for adding a new plugin and saving can be further 
  enhanced, either through code updates within the backend or through 
  frontend enhancements (no reload after save)
   - Alias System
  - We are aware of several issues related to the Alias Plugin, 
  specifically to the recursion issues that can be triggered by content 
  editors. We are working on possible solutions towards the end of next 
week.
   - django CMS 3.3.1
  - We expect a release next week
   - Addons
  - We are heavily working on screenshot tests for 
  djangocms-admin-style to reduce regression errors on uupdates
  - We are working on djangocms-boilerplate-webpack for Aldryn
   

We hope you find this useful - let us know. 

With regards, 

Angelo, on behalf of the core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/378d4a1a-36a6-4cf0-8c73-4e66c7fffbd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Activity report 21st June 2016

[Angelo Dini]

Dear django CMS developers, 

We want to keep everyone updated better about work that's going on in the 
project, so we are going to try posting weekly bulletins summarising work. 

These bulletins will cover django CMS itself, and also related projects in 
the ecosystem.

What we've done this week: 

   - Released: aldryn-forms 2.1.2
   - Released: djangocms-attributes-field 0.0.1
   - Fix: Permission related tickets on django CMS including public 
   discussions 
    
on 
   how to move forward


Goals for next week: 

   - Permission Cleanup
  - We want to finish the cleanup this week to prepare for future 
  enhancement sprints
  - Help is required on fixing additional issues 
  

   - Make sure the following addons are translatable on Transifex
   - Aldryn Forms (done)
  - Django Filer (done)
  - Aldryn Google Tag Manager (done)
  - Aldryn Locations (in progress)
  - Aldryn Video (done)
  - Aldryn FAQ (in progress)
  - Aldryn NewsBlog (in progress)
  - Aldryn People (in progress)
  - Aldryn Categories (done)
   - 3.3.1 Release Preparations (including 3.2.6 and 3.1.18)
  - We are soon preparing releases for the above mentioned versions 
  mainly addressing minor issues with translations and the toolbar
   - django Filer
  - Catching up maintenance on django Filer with adding "Media Library" 
  to the toolbar and fixing blocker issues
   - We expect to release the following addons for 
   djangocms-attributes-field implementations:
   - aldryn-bootstrap3
  - cmsplugin-filer
  - djangocms-link
   

We hope you find this useful - let us know. 

With regards, 

Angelo, on behalf of the core team

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/de1b6736-edd7-4f68-b7ba-860069a0eb06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.