8000 permissions issue with clean contact on options save · Issue #370 · WPBuddy/largo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

permissions issue with clean contact on options save #370

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.

Sign up for GitHub

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

Jump to bottom
Closed
aschweigert opened this issue Jan 26, 2015 · 6 comments
Closed

permissions issue with clean contact on options save #370

aschweigert opened this issue Jan 26, 2015 · 6 comments
Assignees
@benlk
Labels
priority: low Nice-to-have in a release. type: bug
Milestone
0.5

Comments

@aschweigert
Copy link

From the Appearance > Clean Contact menu, when you hit "save options" the options do appear to be saved, but I get an error page that says "Cannot load clean-contact." instead of just confirmation that the options have been saved.
@aschweigert aschweigert added type: bug priority: low Nice-to-have in a release. labels Jan 26, 2015
@aschweigert aschweigert added this to the 0.5 milestone Jan 26, 2015
@benlk
Copy link
Collaborator
benlk commented Jan 27, 2015

Can you confirm the following URLs?

It looks like the redirect on save is to a page that doesn't exist, namely the clean-contact settings page under general settings. This should be solved by #355's solution.

@aschweigert
Copy link
Author

Yeah, for example:

http://largo.inndev.wpengine.com/wp-admin/themes.php?page=clean-contact
http://largo.inndev.wpengine.com/wp-admin/options-general.php?page=clean-contact&message=updated

Let's get that other commit merged and then we can confirm.

@benlk
Copy link
Collaborator
benlk commented Jan 27, 2015

It's in develop right now.

@aschweigert
Copy link
Author

develop pre-0.4 or post-0.4?

@benlk
Copy link
Collaborator
benlk commented Jan 27, 2015

post-0.4. Should I put those commits in master?

@aschweigert
Copy link
Author

if it's a bugfix that's not going to cause complications for anyone, then i'd say yes. as a separate branch and pull request though so we can be extra certain everything is cool before merging.

@benlk benlk mentioned this issue Jan 27, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benlk benlk

Labels
priority: low Nice-to-have in a release. type: bug
Projects
None yet
Milestone
0.5
Development

No branches or pull requests
2 participants
@aschweigert @benlk
0