Issue: testing on localhost

Check Settings > Options > VaultWiki: Server Settings > Wiki Base URL, and make sure it also uses localhost.
If you are using vBSEO, you may have to disable it on localhost.

I have not had issues myself using VaultWiki on localhost, so there must be a configuration issue somewhere that you're overlooking.

all settings were set to localhost.. appearently it was some unexplained browser caching problem. when trying in another browser it worked fine.
sorry for the inconvenience.

I do however have a question about importing the data from media wiki... at first i thought i was not working.. lots of timeouts untill i set the mediawiki setting to perm db connection..
then it looks like the script is doing nothing...

the screen: Importing mediawiki data
gives a link with the text: processing complete - proceed.
but clicking the link doesnt do anything..
untill after some time i found out the importing is NOT complete.
i found that out when hovering the link and saw the number changing... (perhaps a processing bar/number can be shown here)

the import is really REALLY slow... my wiki has 15.000 pages.. i started the import about 1.5 hour ago.. it has only done 4500 (pages/cycles).. only selected the default namespace.. (excluded all pages from other namespaces)

i am really holding my breath for this if/when i am installing vaultwiki on the live server..

is it perhaps an idea to make a command line script for the import? (like mediawiki has for intensive tasks)

If it was taking a long time, it was probably on the step to import edits, and you probably have close to 1 million of those. There's not much that we can do to improve the speed of copying that many items... all we can do is wait for it to finish.

Like you said, a command line script might help. It would eliminate some overhead of the repeating HTTP request, but I really think that you being a single user on localhost (and not having to connect through a chain of external servers) would have made this negligible anyway.

Since there isn't currently a command line script, and one hasn't really been requested before, you'll have to use the existing import script. I would say that however long it takes on localhost is a very optimistic estimate of how long it would take live.

However, if you are importing from an external IP address into your localhost database, then the latency of this connection is slowing things down a bit. If the original database is hosted on the same machine as your live site, then this effect would be reduced in a live import.