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

Feature Request - Toolbar - Ajax response #2564

Closed
leesolway opened this issue Feb 3, 2014 · 5 comments
Closed

Feature Request - Toolbar - Ajax response #2564

leesolway opened this issue Feb 3, 2014 · 5 comments
Assignees
Milestone

Comments

@leesolway
Copy link

It would be nice if the toolbar method 'add_ajax_item' had a way to pass feedback to the user.. This has already been implemented in case of an error (as shown below), however i can not see a way to achieve this for other use cases (such as user feedback confirmation):

There is a callback method however i do not see how this could be passed from add_ajax_item.

'error': function (jqXHR) {
that.showError(jqXHR.response + ' | ' + jqXHR.status + ' ' + jqXHR.statusText);
}

@digi604 digi604 added this to the 3.0 milestone Feb 10, 2014
@FinalAngel FinalAngel modified the milestones: 3.X, 3.0 Feb 25, 2014
@FinalAngel
Copy link
Member

Feedback is not yet implemented, it is currently only a simple yes/no interaction message.
If confirming, the browser will redirect. You could Implement a feedback using djangos message framework. The toolbar will recognise a message and display it after a reload.

Otherwise we will reconsider on 3.1

@FinalAngel FinalAngel modified the milestones: Clean up issues & pull requests, 3.X, 3.3 Oct 29, 2015
@mkoistinen mkoistinen modified the milestones: 3.3.1, 3.3.0.RC1 May 16, 2016
@czpython
Copy link
Contributor

czpython commented Jun 9, 2016

@vxsx anything to add?

@czpython czpython assigned vxsx and unassigned FinalAngel Jun 9, 2016
@vxsx vxsx modified the milestones: 3.4, 3.3.1 Jul 8, 2016
@czpython czpython modified the milestones: 3.4.x, 3.4 Sep 19, 2016
@JustDevZero
Copy link

Is this solved in 3.6 or 3.7? Because I don't find where from 3.4...

@Aiky30
Copy link
Contributor

Aiky30 commented Sep 18, 2020

@leesolway @JustDevZero Is this still a valid issue?

I can see that there is the ability to add the yes / no feedback as FinalAngel mentions above.

If this is still a valid issue, what would be a use case / scenario of how such a feature should work?

@Aiky30 Aiky30 self-assigned this Sep 18, 2020
@Aiky30
Copy link
Contributor

Aiky30 commented Oct 1, 2020

Hello @leesolway,

Thank you very much for your contribution to the django CMS project. The django CMS project has recently joined forces under the banner of the newly founded django CMS Association to revive the development of django CMS. For this reason we have analyzed all pull requests and issues in detail and decided which ones fit the product vision we want to go with django CMS.

Due to the age of this issue we are unable to safely accept the contribution. If you feel this issue is still required please inform a member of our technical committee: nicolai@django-cms.org.

Nevertheless we thank you for your participation and would like to emphasize that we do not want to discourage you in your contribution to the django CMS project. On the contrary, we encourage everyone who is interested in the success of django CMS to join us!

If you want to learn more about the work of the technical committee, our product vision and how you can become a member of the dCA, you can find all information here:

We are looking forward to every companion who would like to shape the future of django CMS together with us!

If you have any questions, feel free to reach out to Nicolai, our Community Manager: nicolai@django-cms.org

Sign up for the Association now!

@Aiky30 Aiky30 closed this as completed Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants