[Solved] Bug in moving WB into another dir?

[Boudi]

Hi there,

Thnx to the attention of other WB users it seems like there's a bug or something:

Example:

1) You build a WB website in a testdir and provide it with input.
2) When done you move the entire website and db into another dir.
3) All of a sudden behind all the [wblink] and [link] there appears a ?phpadmin code behind it. Example:

Code:

[wblink47]?phpMyAdmin=fQP2hqlz6s4S7kjzh74jqd%2

What could cause this?

Boudi

[Ruud]

did you do something with phpMyAdmin to replace data in the database or export <> import to a new database?

To me it looks like a phpMyAdmin sessionId. WB will not put it in, and the data that was included is very much pointing to phpMyAdmin.

[Boudi]

Hi Ruud

did you do something with phpMyAdmin to replace data in the database or export <> import to a new database?

Yes, sort of.

What I do to make a site 'live' (move to another directory) is:

- export the enitre wb db via phpadmin
- move all files through ftp
- delete all the paths in the db eg: testarea/
- save the db
- delete the original db via phpadmin
- import the edited db via phpadmin
- change the paths in the config.php

That's it.

[Ruud]

Do you still have the edited .sql import file?
My guess is something went wrong there.

[Boudi]

No I don't have that any more.

- But what I did was openend the exported db with wordpad.
- Did ctrl+h
- Deleted the old dir in which the website was build in (eg: testarea/) by replacing testarea/ with noting
- Saved the new db with another name (in case of)
- Deleted the current db in phpadmin
- Imported the new db in phpadmin

[Boudi]

Ok, after some serious deep investigation with Ruud ( in other words, Ruud alone  ) the source of the problem was not some hacking stuff but a tiny bug in the phpadmin that causes this.

To avoid this kind of nasty stuff in your codes: export/import the db as a zip file instead of a txt file.

A thnq and a bunch of flowers to Ruud.