VaultWiki Broke My Site

[Skylab]

My site is: http://artoftravelblogging.com/forums/

After the installation of VaultWiki, it seems several things have gone wrong. First most important thing is that nothing is saving. Editing user profiles do not get saved. Seems like it's all across the forums where nothing is getting saved. Colors in my StyleVar seem to have gone missing. Not sure what happened to my navbar that it's now a different color on hover or the submenus are now all white. Several other colors have changed.

I'd love to purchase the product but I'm having huge issues with it on fresh install.

Products used are:
aMember Pro Integration
DragonByte Tech: Advanced Post Thanks / Like (Lite
DragonByte Tech: vBActivity & Awards (Lite)
DragonByte Tech: vBCredits II Deluxe (Lite)
DragonByte Tech: vBMail (Lite)
DragonByte Tech: vBShop (Lite)
Tabs en vBulletin 4.x
vB Optimise Lite
VSa - Advanced Forum Statistics

Let me know what information you need so I can get this running.

[Skylab]

I know I only posted this an hour ago but the quicker we can get this working, the better. I'm willing to pay for the license but I need to ensure that this even works because right now it doesn't seem like it. Thanks!

[pegasus]

If you're getting Javascript errors, you'll need to look at your browsers Error Console and post what's there.

As for colors in your StyleVars, did you upgrade vBulletin recently? They removed a lot of StyleVars in the last two versions.

[Skylab]

I just upgraded 30 minutes ago because of the issues I was having and thought perhaps upgrading might solve the problem but it didn't.

When posting, it seems it's caching everything to the extreme. I have to hard refresh CMD + R in order to view anything that I do including posting, saving profiles, making changes to the wiki, etc. This only started happening after installing VaultWiki which I thought was odd. I haven't done anything else to the site in ages.

[Skylab]

I also created a ticket over at vBulletin and just got this from them:

Hello,

Something on your server configuration is telling html/css to have expires header in the future, as in when it should expire that page and your browser will re-request a new version


Key Value
Expires Fri, 30 Mar 2012 22:33:05 GMT

Do you have anything like that setup?

You shouldn't send expires headers on html/xml content.

No idea how that got in there.

[pegasus]

VaultWiki doesn't modify any server configurations. You will need to deal with that expires issue and possibly clear your browser cache to rule that out.

It's possible your server is just set to expire all requests at the future date. Contrary to vB support's response, it is perfectly acceptable to send future expires headers on static HTML/XML content, so this may have already been set on your server. What you don't want is to send expires headers for HTML content if that content is updated frequently. So you either need to send the expires headers for specific pages on your site, or only specific file types.

[Skylab]

Alright I'll check it out. Thanks so much for the help! So random that it started happening directly after installing VaultWiki although it had nothing to do with it. Anyway -- I'm excited to get started on it as I have a membership site that would absolutely love this.

[pegasus]

If you can't find a server setting for this, it might be a "feature" of vB Optimise Lite, since technically setting expires headers in the future could be considered an optimization.

[Chris]

vB Optimise does quite a bit of that listed above...get rid of it and see how you fare.

[Delfi_r1]

I have a problem, perhaps related: I log as admin, with all group permissions set to yes and I can't edit pages.

[Delfi_r1]

Excuse me: I have the pages edition set to moderated even If I have all permissions and the wiki forum is not moderated.

[pegasus]

Check if your wiki forum has custom forum permissions. Also, forums don't need to have a moderator to be moderated - admins and super-mods can still do it. Moderation is typically handled by a permission, but sometimes it can be applied to anyone's post if the post triggers a false positive in vBulletin's SPAM scans.

Since you're using the latest vBulletin I don't think you have the bugs with permissions storage, but it might be one of those other things.

[Delfi_r1]

I've managed to clear it at admin level, now I need to finetune the users permissions for the target group. Thanks.