Attachment uploading permissions error

[Moses]

Hello,

I upgraded to VB4.1.0 PL2 and Vaultwiki 3.0.9 yesterday, and now have a permissions error when attempting to upload to the image namespace.

Moses, you do not have permission to access this page. This could be due to one of several reasons:

1. Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
2. If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

I can still upload to the forum, and I am an admin so should have permissions everywhere.

Thanks,
Moses.

[pegasus]

When the Manage Attachments popup appears with the no permissions error, check the URL. Does the contenttypeid in the URL have a value?

If not, the content type cache probably needs to be rebuilt. In Settings > Options > Server Optimization Options > Disable Content Caching, set it to Yes. Then attempt to add an Image attachment again. Once successful, change the setting back to No.

[Moses]

Thanks Pegasus,
That was it, original URL was
http://www.greenandgoldrugby.com/for...ent.php?values[f]=63&contenttypeid=&poststarttime=1294528058&postha sh=30f2ce5fadd54bc0fcfc2efd44cdd869

with no contenttypeid a you suggest. I disabled content caching and it works, directing to a URL of
http://www.greenandgoldrugby.com/for...ent.php?values[f]=63&contenttypeid=17&poststarttime=1294528969&post hash=e0a80237f4b50c22ff336b0b473a1e64

When I re-enable the caching however, it breaks again. URL is:
http://www.greenandgoldrugby.com/for...ent.php?values[f]=63&contenttypeid=&poststarttime=1294528878&postha sh=45236c959787667e995d74470fd43620

I'm still using the classic uploader, fancy new one was too confusing for my members.

[pegasus]

If you have the vBulletin CMS installed and enabled, you can manually clear the cache by going to vBulletin CMS > Clear CMS Cache. If you don't have it installed, you might be able to rebuild it by disabling the VaultWiki product, then re-enabling it using the default Product Manager.