I understand all of this thread and pleased to see others have this issue but I want my members to have this feature back. I am getting nailed on this as they are used to something. You really can't give something to someone like this and just yank it out from under them. It isn't right nor fair. Now if they never had this feature then yea this would of been okay. I am not mad or anything just wanting a fix. I am hoping that what was posted above is true and can we get a php file for both to overwrite the current.? There should just be a setting in the admin panel to allow or not I think. This way you have the best of both worlds as I know users were wanting this feature to post only on the CMS page. So I beg of you Devs to please post the 2 altered php files to overcome this so some of us can have this feature back. Yes I went and redid all the permissions to no avail.
VBCMS Comments
Collapse
X
-
-
I understand all of this thread and pleased to see others have this issue but I want my members to have this feature back. I am getting nailed on this as they are used to something. You really can't give something to someone like this and just yank it out from under them. It isn't right nor fair. Now if they never had this feature then yea this would of been okay. I am not mad or anything just wanting a fix. I am hoping that what was posted above is true and can we get a php file for both to overwrite the current.? There should just be a setting in the admin panel to allow or not I think. This way you have the best of both worlds as I know users were wanting this feature to post only on the CMS page. So I beg of you Devs to please post the 2 altered php files to overcome this so some of us can have this feature back. Yes I went and redid all the permissions to no avail.
*edit* I've just fixed it myself based on what Mystics said:
Comment out line 317 to 320 in showthread.php.
PHP Code://if ($thread['forumid'] == $vbulletin->options['vbcmsforumid'] AND !can_moderate($thread['forumid']))
//{
//eval(standard_error(fetch_error('invalid_comment_forum', $vbphrase['forum'], $vbulletin->options['contactuslink'])));
//}
Replace the following
PHP Code:if (!$foruminfo['forumid'] OR ($foruminfo['forumid'] == $vbulletin->options['vbcmsforumid'] AND !can_moderate($foruminfo['forumid'])))
PHP Code://if (!$foruminfo['forumid'] OR ($foruminfo['forumid'] == $vbulletin->options['vbcmsforumid'] AND !can_moderate($foruminfo['forumid'])))
if (!$foruminfo['forumid'])
Last edited by fogjuice; Sat 19 Jun '10, 12:08pm.👍 2Comment
-
Turn the permissions off in forum permissions and turn of search indexing for vbcms comments and that should stop it from showing up, I think.Comment
-
-
Yes it works! I think they need to incorporate a setting in the options settings of the admin panel to allow or not then we won't need to go through and do this manual edit.Comment
-
Yeah, I am having the identical issue. As an Admin, I can see the links fine, but all of the non-admins are reporting the same no permissions error.
The permissions are set correctly.
I have to admit - this issue confuses me a little bit. It sounds to me like in 4.0.4 - an attempt was made to remove Article Comments from appearing in What's New? I can't figure out why this would be considered a good idea. I would think you would want your users to view comments on articles in this fashion....Comment
-
Correct I know I want this feature to remain as it was. I already did the edit needed to make my users happy again. Worst part this thing wasn't mentioned in the release notes that is what scares me.
Yeah, I am having the identical issue. As an Admin, I can see the links fine, but all of the non-admins are reporting the same no permissions error.
The permissions are set correctly.
I have to admit - this issue confuses me a little bit. It sounds to me like in 4.0.4 - an attempt was made to remove Article Comments from appearing in What's New? I can't figure out why this would be considered a good idea. I would think you would want your users to view comments on articles in this fashion....Comment
-
I am going to try and do the edits mentioned above because I am getting countless PM and pings on the errorComment
-
I would like the option to use it or not ... and I agree 100% that it wasn't mentioned in the release notes and that's a huge issue and shows a possible breakdown in release and change management process.
I am going to try and do the edits mentioned above because I am getting countless PM and pings on the errorComment
-
Oh, I just submitted a ticket for this, I guess I wasnt alone.
Terrible, terrible bug. My users are complaining about this, they've grown to like the vbcms forum.
I'll try the edit mentioned above, but I hope this is fixed soon, even with a patch.Comment
-
Well it looks like vb offically can't win! People complained about the comments showing up in the forum so they come up with a solutions and fix it and now people complain that they don't show up.
Only thing I'd complain about is the fact that the threads were still showing up in the search.Comment
-
Well it looks like vb offically can't win! People complained about the comments showing up in the forum so they come up with a solutions and fix it and now people complain that they don't show up.
Only thing I'd complain about is the fact that the threads were still showing up in the search.
But removing easy access to those comments isn't a solution - it's just taking it away. And doing so halfway, so that the posts are still showing up as new, but you can't view them. If they want to change the way the comments are stored and displayed, that's fine, but they still need a mechanism so that users can quickly and easily see what articles have new comments via the What's New...
Even if you have no problems with the idea behind this change, there is still something physically broken here that needs to be fixed. You should never have a situation where users are able to click something that returns a no permission message....Comment
-
I never flamed either I was just asking for a fix. Also note I suggested this be a feature to enable or disable. Then gave constructive criticism on the not releasing this info in the release notes. Never once did I complain.Comment
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Comment