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

popup not refreshed when click on users in meteor 0.8.2 #2

Open
dougserfass opened this issue Aug 7, 2014 · 4 comments
Open

popup not refreshed when click on users in meteor 0.8.2 #2

dougserfass opened this issue Aug 7, 2014 · 4 comments

Comments

@dougserfass
Copy link

in manage-roles.js, Template.editRolesForm.rendered is only called the first time the template is rendered
as a result, in meteor 0.8.2, popup is not refreshed when click on users
in other words...popup is only correct for first user clicked

@alanning
Copy link
Owner

alanning commented Aug 8, 2014

Right, the example is only valid for pre-blaze meteor (due to how template rendering has changed).

If you'd like to submit a PR with blaze compatibility that would be a big help!

On Aug 6, 2014, at 8:52 PM, dougserfass [email protected] wrote:

in manage-roles.js, Template.editRolesForm.rendered is only called the first time the template is rendered
as a result, in meteor 0.8.2, popup is not refreshed when click on users
in other words...popup is only correct for first user clicked


Reply to this email directly or view it on GitHub.

@dougserfass
Copy link
Author

i fixed the problem in our app for now by brute force...i do a location.reload() after cancel/save on popup...not a good solution, but our app is a prototype
what specifically do i do to submit a problem report with blaze compatibility other than to say the sample app popup does not work correctly with blaze?

@alanning
Copy link
Owner

alanning commented Aug 8, 2014

Ah, PR generally stands for pull request. :-)

It's a github thing where you can send updated code to fix issues or add features.

On Aug 8, 2014, at 4:09 PM, dougserfass [email protected] wrote:

i fixed the problem in our app for now by brute force...i do a location.reload() after cancel/save on popup...not a good solution, but our app is a prototype
what specifically do i do to submit a problem report with blaze compatibility other than to say the sample app popup does not work correctly with blaze?


Reply to this email directly or view it on GitHub.

@dougserfass
Copy link
Author

sorry for not understanding all of the github lingo
also, let me say that we could not have created our app in such a short time without meteor-roles and meteor-modal-example
i am not sure you would want to integrate my blaze compatibility fix (adding location.reload() to cancel/save) into your project as it really is not a long term solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants