Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Structure and content modes are outdated in the docs #6694

Open
DmytroLitvinov opened this issue Jun 27, 2019 · 3 comments

Comments

Projects
None yet
3 participants
@DmytroLitvinov
Copy link

commented Jun 27, 2019

Summary

Seems like docs is outdated for djangoCMS 3.6 because in the cms_toolbar we don't have explicit switcher from Structure mode to Content mode and vice versa.

Expected behaviour

See at the top of the site(in djangocms toolbar) switcher from Structure mode to Content mode and vice versa.
image

Actual behaviour

See only one button which related to Structure mode.
image
image

Environment

  • Python version: 3.6
  • Django version: 2.1
  • django CMS version: 3.6

Additional information

Related to issue #3423

@FinalAngel @czpython I am ready to prepare PR for outdated doc if you need help.

@FinalAngel

This comment has been minimized.

Copy link
Member

commented Jun 27, 2019

That be great @DmytroLitvinov :)

DmytroLitvinov added a commit to DmytroLitvinov/django-cms that referenced this issue Jun 27, 2019

@DmytroLitvinov DmytroLitvinov referenced a pull request that will close this issue Jun 27, 2019

Open

Fix content mode related to #6694 #6696

2 of 11 tasks complete
@tarasyyyk

This comment has been minimized.

Copy link

commented Jul 6, 2019

Hi, I'm newbie to Django CMS. There aro issues I found in documentation:
1  Installing django CMS — django cms 3 6 0 documentation 2019-07-06 15-23-30
1  Installing django CMS — django cms 3 6 0 documentation 2019-07-06 15-20-22

@DmytroLitvinov

This comment has been minimized.

Copy link
Author

commented Jul 7, 2019

Hello @tarasyyyk ,

You should create a separate issue ticket for that case.
Also, it would be great, if you could provide PR for fixing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.