Issue: VW 3.0.2 to 4.0.0 RC1 upgrade error

I would highly recommend submitting a Ticket Support service at this point (via the Members tab).

You may have an opcache enabled on your server machine that is preventing any edits from taking effect until the cache expires, and the only person who knows when that is is the person who installed it (may not be you). That edit worked for myself and another user who was having the same problem. However, I know that with Zend Opcache turned on, I sometimes need to hard reset PHP in order to see changes take effect.

Okay, I've gone ahead and gotten your site all upgraded and imported. If anything's missing, let me know.

Remember that 4.0.0 contains major changes. There are new permissions that you probably need to review, and there's plenty of other changes that you should just keep a lookout for. We tried to make the wiki easier to use in version 4, but if you had managed to get used to the old ways of doing things, you might be a little confused at first. If you need any help finding what happened to a particular function or want to learn about one of the new features, don't hesitate to ask.

One question ... on this page (as an example)

How do I get the attached images to embed and display directly inline (or in a table) like they were before.

When I go into Edit mode, they show up inline just fine, but when the page displays it shows a link "AttachmentXXXX" that displays the image if you click on it. I'd just like them to show up inline. Is there a setting that toggles this?

By the way, thank you for importing. Were there any errors or mis-configurations that I should know about as far as the installation was concerned?

If the page shows an "Attachment [NumberXY]" link, then that means the image was originally uploaded using vBulletin's attachment system, rather than VaultWiki's attachment system. I thought the importer was supposed to convert these automatically, so if you can find one, please send it my way and I'll have a look. If the editor is showing the images, but the page is not, the editor behavior is a bug that we will need to look into, since the editor should not show you things that won't work after you hit save.

To include wiki attachments from now on, you should have an editor button like this:
It should open a nice dialog where you can select images from a list, upload new ones, and choose various display options.

Regarding the import, I don't believe there were any errors related to misconfigurations. The only thing I ran into was that the installer skipped the step to create the wiki index page. I have not seen this occur before, I'm still investigating why that step may have been skipped.

There were a few compatibility issues with your version of PHP, but I patched them on VaultWiki's end and the related code seems to still work as expected. Some versions of PHP that are within our minimum requirements still have bugs that lead to unexpected behaviors or error messages.

Here are a couple of illustrations of what I meant, at this URL (as an example):

http://www.500eboard.com/forums/wiki...eference-Guide

Wiki table as any member would currently see it.

https://db.tt/KXDZ2ahU

Wiki table shown in editor mode (photos displaying inline correctly).

https://db.tt/Qz78LaLj

Okay, I've gone back and you should now have a list of the proper BB-Codes to use for those attachments. In each page that has attachments, there will be a list at the bottom that shows the appropriate replacement BB-Codes that will work inside wiki pages. It's just a question of swapping them out where needed.

Just as a point of follow-up, I have gone through most all of my Wiki pages and re-embedded the attachments that showed up at the bottom of each page. A bit of a cumbersome conversion process, but had to do it. Thank you for the assistance with/prep for this effort.