— hartnell

for the empty folders.. i can confirm this problem, but nothing more :/
this should not happen in an ready image.. though for me it might is caused by virtualbox.. but then again.. he is using vmware and has the same problem

—Ano

though, accessing the / site gave me just

Not Found

The requested URL / was not found on this server.
Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu4 with Suhosin-Patch Server at localhost Port 8080

(port 8080 is forwarded to 80)

i thought this is a ready to run image? :/

after inspecting the logs it seems that it accesses the file /wikidot/www/wikidot1/web and that the file does not exist

oh and btw, why is there alsa installed?!
i could setup a virtual debian server for vbox with all configs done

edit: ok i should read more : 5. Before you launch it look at the settings and configure the Shared Folders — "wikidot1" or "wikidot2" must point to the locations where you have a working copy of Wikidot.

so nm that, going to try that now

—Ano

 sudo su - 

Do you suppose this is what I need to use with the virtual machine? I would have tried it already but I'm trying to download the VM again (6th try!) hoping to get a clean copy.

See if that helps….

-gmhelper

P.S. I am also interested on how to work the Virtual Version coz I have installed it on my PC.

I downloaded the VM as required, and got what I think is a clean copy, tho it took several tries

• wikidot-dev2-vm-20080220.tar.gz (603,068 KB, or 617,540,980 bytes)

I tried using PowerArchiver and TUGZip, but neither was able to decompress everything for some reason. Neither generated errors, tho. By merging the two uncompressed versions, I was able to get a VM that booted up, but apache failed during startup, and the /wikidot/…/wikidot1 and wikidot2 directories were empty.

When I tried to shut down the VM, I kept getting an error: "Must be root", but I do not know what the root password is. It isn't "wdadmin", as it is for the wdadmin account. I had to force a "power-failure" shutdown in WMWare Player just to turn the VM off.

Any help you can provide would be appreciated.

Thanks,

David.

It's been over two weeks since your reply and nothing has changed. (And a month since I originally provided the detail in bug reports.)

I would sign your contribution license and commit the fixes to wikidot v1 myself if I had any assurance that the changes would flow through to the wikidot.com website in a timely fashion. However, there's nothing published showing how the two connect with planned releases, etc.

Perhaps the virtual-machine page could mention which VM version this was exported from;
I was not able to open it in VM-Player 1.0.4 or 1.0.5.

I'd rather not use the WM-Player 2.0 Beta because it might disturb other VM's on this hardware!

Can someone with subversion access update the open source version as well?

michal

Everything else is described in the "debian quickstart".

m.

For the record here are the bug reports:
http://community.wikidot.com/forum/t-22246/module-newpage-doesn-t-honour-template-selection
http://community.wikidot.com/forum/t-46381/many-blank-templates-appear-in-template-list

So, I'm wondering if there is a better way to get bugs fixed. If source code changes are made on the open source Wikidot v1 repository, do the changes flow through to wikidot.com blogs? If not, can the relevant patches be sent through to another destination, e.g. email address? If so, what is the delay between changes to the repository here and the live wikidot.com wikis?

Thanks.

If I were to move V1 Wikidot to another hosting server that has PHP 5.2.x, are the bugs you fixed listed in one of the changelog? Were there workarounds in the code base for some or all of the PHP bugs?

I know V2 is taking lots of cycles and it may be that the bugs you refer to only show up in V2 Wikidot; only PHP bugs related to V1 are of current interest to me. Any pointers would be appreciated.

Are there any other tables that need records added or updated?

On a related note (for purely selfish reasons!), are there any plans in the works to allow wikidot.com users to create an export of their wiki sites that could be imported into an open source install? I realize that extra steps would be involved with file attachments, etc., but it would be a nice feature to make a full backup/restore of a site easier.

-Ed

yes, we want to implement such functionality in WD2 and this could be done in at least 2 ways (btw: now it is a good time to discuss which is better):

1. Draft/unpublished mode

One could edit pages and save without publishing. This would mean that a page (or whole wiki) could have 2 versions: current and published. This would add extra structures to the site and myself I am not a big fan of this solution because I find it lacking flexibility.

2. Cloning & merging back

To keep a page/category/wiki in a consistent state one does not edit live pages, but instead "clones" a page/category/wiki and makes changes to the working copy. When changes are done (and reviewed), they can be merged back to the original source. Since the clone operation links the original and cloned content, merging back should be easy and straightforward.

The solution 2 is inspired by how distributed version control systems work (e.g. Mercurial or Baazar). If we can implement a nice merge tool, several people could easily work on the same document (different copies) and push the changes back to the original container.

IMHO it gives nice flexibility and could be adapted in various workflows. The clone-edit-review-publish would nicely work with the permission system.

We are not really planning this for the "alpha release" of WD2 (in the next few months) but this is a must eventually. Michal Bartoszewski (e1n) is working on adapting a 3-way XML merge tool (I think this one) to this scenario but any help from XML experts would be highly appreciated.

best,
Michal

Any thoughts on doing a similar operation on Wikidot, either 1 or 2? One site I know of uses port 8080 for staging and 80 for production, while another has two URLs, one for each type.

If there were a quick "restore from zip" mode, I could zip the staging WD server and restore the zip to the main WD server, after first clearing it (deleting it?). Something that doesn't involve requests to the WD admin so I can roll forward/roll back as needed.

Thoughts, suggestions. WD2 solution already in the works?

TIA

Thank you for the quick reply and quick fix! I applied the new php file and "recompiled" the pages and everything is working well now. Hopefully, that will be the last hurdle.

Thanks again for all of your work on this project.

-Ed

Now Tidy is back and buttons and collapsible blocks should work. Already commited to svn.

thanks,
Michal

PS. I think you will have to "recompile" the affected pages, i.e. edit them (a bit) and save the top-nav.