Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Dashboard resets our changes - Users unable to edit their posts
tatortodd22
New
Old discussion of similar issue, unresolved and outdated = http://vanillaforums.org/discussion/27605/authors-can-not-edit-messages
This issue happens across all platforms. We are using Vanilla 2.1.10
Issue: Our users are unable to edit their own posts. We want to change that setting.
- In the Dashboard, we go to Forums>Advanced. We then set Discussion and Comment Editing to "Authors may always edit." We click save.
- The users have no edit button on their posts within the thread.
- If the user browses the discussions, there is an edit button on the entire discussion. This should only be there for administrators and moderators.
- When the user attempts to edit this way, they are brought to a "Page Not Found" page.
- When you exit the dashboard and return, the change in the setting has reverted to "Authors may never edit".
I only know basic HTML/CSS. If you have a solution more complicated than that, please include step by step instructions. Thank you very much for your help.
0
Comments
Please confirm the line
$Configuration['Garden']['EditContentTimeout']
in your/conf/config.php
file.Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.
Hi @hgtonight! @tatortodd22 and I are working on this problem together.
The
config.php
reads$Configuration['Garden']['EditContentTimeout'] = '-1';
We cannot change the setting in the Dashboard, and if we try to hard-code a time into the config.php, it doesn't help.
We installed via GoDaddy at 2.0.8 and manually upgraded to 2.1.10 (following all the steps provided by vanilla).
We really want to avoid doing a re-install as the community is already active (and I believe this problem would just manifest itself again when we upgrade).
Before you ask, it's not a plugins problem, as this occurs when all are disabled.
I read another forum post in which someone said it could be a caching issue, but no remedial steps were given.
Here are the contents of our
config.php
Here are the contents of our
.htaccess
Any help is appreciated.
Firstly, thanks for using my addons!
Secondly, are you using a rank perk that changes the Edit Timeout dynamically?
Thirdly, your current config shows
$Configuration['Garden']['EditContentTimeout'] = '5600';
which should give you a timeout of about 1.5 hours.Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.
We will look for a rank perk and see if that's the issue.
As I mentioned above, the edit timeout is hard-coded, but doesn't actually allow the user to edit their discussions or comments.
@mattdonatelli you posted a lot of credentials with your config details that you really aught to change now. Specifically the social networking stuff and the Captcha.
Be careful. If it looks like private information it probably is. Make sure to censor you config file next time.
grep is your friend.
@hgtonight You're a genius!
It was being overridden by settings inside YAGA's rank perks. These default to Users May Never Edit in the timeout setting.
Humble suggestion, maybe make them default to "default"? Or inherit the settings from Garden? (Not sure how that all works, I'm a novice for sure).
Great plugin by the way, our forum goers are loving it!
Thanks again.
Matt
The default configuration uses the first rank as a "probation" rank that disables a lot of "nice" things until you level up. Feel free to customize your ranks to your taste/community.
Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.
@hgtonight That makes sense! I bet we just missed that part in the documentation.
I am having this same issue. Are there any steps I can take to fix the YAGA rank perk issue that is causing this? @mattdonatelli @hgtonight
Please do not post on three year old posts... specially if they have nothing to do with
your problem.
❌ ✊ ♥. ¸. ••. ¸♥¸. ••. ¸♥ ✊ ❌