8000 Publishing a page shows form instead of reloading new content · Issue #402 · django-cms/djangocms-versioning · GitHub
[go: up one dir, main page]

Skip to content
Publishing a page shows form instead of reloading new content #402
Closed
@jrief

Description

@jrief

There seems to be a regression in the sources making up django-cms/cms/static/cms/js/dist/4.1.0/bundle.toolbar.min.js. This bug is not visible yet to users installing django-cms from PyPI, but it will be as soon as we rebundle the JavaScript files.

How to reproduce:

  • Check out the latest version from django-cms in branch develop-4.
  • Bundle the Javascript sources: Run gulp bundle.
  • Check out latest version from https://github.com/fsbraun/djangocms-versioning/tree/feat/timed-publication (the bug presumably also is reproducible with master from upstream).
  • Open a page.
  • Make the page editable, but do not edit anything.
  • Publish the page. This will create a POST request such as /de/admin/djangocms_versioning/pagecontentversion/45413/publish/ and works as expected, ie. the user sees the edited page again.
  • Make the page editable again.
  • Edit a plugin and save it.
  • Publish the page. This now will create a GET request such as /de/admin/djangocms_versioning/pagecontentversion/45413/publish/. This opens a form with some time constraints and is not expeted.

By copying the latest bundled file from https://github.com/django-cms/django-cms/blob/develop-4/cms/static/cms/js/dist/4.1.0/bundle.toolbar.min.js to its local destination at django-cms/cms/static/cms/js/dist/4.1.0/bundle.toolbar.min.js this workflow works again as expected.

Conclusion:

  • I assume that this is a regression somewhere in a JavaScript file.
  • I also assume that when using the official main branch, then we get a permission denied, because of this statement (haven't tested yet).

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0