$dir = preg_replace(';/$', '', $dir);

should be:

$dir = preg_replace(';/$;', '', $dir);

A semi-colon was missing after the $ sign.

Sorry it took so long for me to catch that (if that is indeed the cause of your issue).

See this thread: http://www.wikidot.org/forum/t-55928/wikidot-after-install

-Ed

This link:

http://svn.wikidot.org/svn

Gives this error:

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

---

Apache/2.2.3 (CentOS) Server at svn.wikidot.org Port 80

 You have been inactive quite a long while trying to log in and your session data have expired. Please try to click 'log in' once again. 

 GRANT ALL ON ts2.pg_ts_cfg, ts2.pg_ts_cfgmap, ts2.pg_ts_parser, ts2.pg_ts_dict TO wd; 

I get:

 ERROR: relation "ts2.pg_ts_cfg" does not exist 

I understand that the tables are in a different place. I have also manually changed ownership of those tables to wd to no avail. Am I missing something here? Why am I not able to log in? I can get the VMware dev image working just fine. Has something changed since 137?

At first blush, it appears that quite a few things have been taken care of and improved with the latest version compared to the version I'm running on my production machine at work (went live back in late March / early April).

Thanks to all of the developers for the hard work! It's very cool that Wikidot Version 1 is still being improved while Version 2 is in full development mode.

-Ed

Although, Ed, you've certainly proved to me that you have quite a bit of mastery. Or maybe you're a Google ninja like many of us. Anyways, I could not have gotten to login screen without your published research. Thanks.

You're welcome. I like the term Google ninja! I'm do rely heavily on Google to find answers when I'm stuck. I used your guide yesterday to try to set up a working system with Unbuntu 8.04 and was able to log in OK as admin, but when I created a new "sandbox" wiki it showed that I wasn't logged in and all attempts to login to that site failed. I did stay logged in to the "master" site, however. I didn't have time to dig, so I'm not sure what the deal is yet.

I think I'm going to wipe my test server and try again from scratch and do a better job of documenting my steps this time.

Stay tuned!
-Ed

 You have been inactive quite a long while trying to log in and your session data have expired. Please try to click 'log in' once again. 

I'm using Postgresql 8.3 and I've checked and all pg_ts_* tables are owned by wd. I'm still getting the error. Are there additional considerations with version 8.3? As Michal pointed out, the tables are now in the pg_catalog schema.

As I am, like Ed states, a bit of a noob to some of this, I'm following the Wiki quite literally (cut/paste) without fully understanding the underlying logic. Although, Ed, you've certainly proved to me that you have quite a bit of mastery. Or maybe you're a Google ninja like many of us. Anyways, I could not have gotten to login screen without your published research. Thanks.

The Ubuntu 8 system that I am using is not virtual (is nonvirtual a word? Oddly, it could be.) so it's a bit harder to roll back changes. I'll do the next install on a VM and take copious snapshots. But first, perhaps someone has a different set of psql commands for 8.3 that work?

hope this help.
Giovanni

• A polling system, a la http://www.urbandictionary.com
• The ability to lock the creation of sub-wikis to administrators only.

If anyone here is familiar with the WikiDot, and might be able to give me a guess as to how difficult the above changes might be, please let me know your opinion.

Below is the project proposal. Feel free to peruse.
Thanks,
Sean

Wikimentany.org (?)

Project Phase:

• Reserve wikimentary.org
• Begin work with wikidot.org developers
• Broadcast idea
• Implement WikiDot server (w/ updates)
• Finalize rules and procedures
• Promote site & begin process

What it is:

• A web site designed similarly to http://www.wikidot.com
• Allows for wiki and forums for open Documentary Projects (controlled by the individual directors)

Advantages:

• Wikimentary will be a social network for the growing movement of viral video-loggers documentarians who have so far acted individually
• Will allow for a division of labor of the video-loggers so that the most efficient at certain tasks can concentrate their time on these tasks
• Will promote a more professional and user-interactive/Web 2.0 approach to video-log documentaries

Disadvantages:

• Documentaries will tend to Illustrative rather than Observational style; many ‘talking heads’ rather than ‘real’ footage
• Documentaries will tend to be shorter and free, not tailored for DVD distribution or network/cable broadcast

Individuals and Roles associated with a Documentary Project:

• Steering committee: controls main Wikimentary site & appoints the members of the Authorization committee
• Authorization committee: accepts & votes on new documentary projects; creates the sub-site & forums for the project and hands them to the director; authorizes changes in the nature of projects; closes old & invalid projects; accepts or rejects finalized documentary for publication & then publishes it
• Director: workhorse; controls wiki edit authority & discussion authority; decides what to put on script
• Director's guild: list of directors
• Narrator's guild: list of voice talent that shows language, dialect, skills, availabilities
• Resources/Specialists: academics, journalists, etc. who have/will act as experts on a topic
• Assistance committee: people who know what to do to create documentaries & can answer questions; will produce a FAQ & walkthrough on how to make a documentary; help with copyright questions, etc.
• Editor's guild: list of individuals with video editing software (must ensure that they’re legit and registered!)
• Director's Assistants [DA’s]: unaffiliated contributors who do most of the work; add new ideas to projects, edit scripts, find multimedia

Main page:

• Edited by the Steering and Authorization committees only
• Lists open and closed Documentary Projects, Director's guild, Narrator's guild, Specialists/Resources, etc.
• Shows popularity up-down voting poll of what people want to have upcoming, á la http://www.urbandictionary.com

Documentary Projects:

• Three levels of copyright:
  • Full commercial copyright
    • Director can make money; Wikimentary will not make money, and the Authorization committee will not finalize the project; the Assistance committee may or may not offer free assistance
  • Creative-commons (commercial)
    • Director can make money; individuals and business can copy and display the documentary for free; Wikimentary will not make money, but will provide assistance
  • Creative Creative -commons (non-commercial)
    • Neither Director nor Wikimentary can make money on the project
• Must have printable release forms for interviews & other legal documents
• Lifecycle:
  • Director proposes a project to the Authorization committee, including main topics, copyright level, etc.
  • The Authorization committee polls the user base for opinions or directly authorizes the project
  • The Authorization committee creates the project’s wiki and forums, then grants administrator access to the Director
  • The Authorization committee and Director recruit members to act as DA’s
  • The Director and DA’s debate content on the forum, gather multimedia, and write the script
  • The Director recruits and interviews Resources
  • The Director recruits Narrators, if necessary
  • The Narrator reads the script, if necessary
  • The Director recruits the Editor
  • The Editor assembles and mixes the final documentary output
  • The Authorization committee reviews the finalized script and output for style, format, and usage or copyright violations
  • The Authorization committee votes on finalization of the project
    • If partially failed, the Authorization committee will request the Director to complete a list of outstanding actions necessary before finalization can succeed
    • If totally failed, or at any time during the lifecycle of the project when deemed absolutely necessary, the Authorization committee may unilaterally delete the project entirely, or may assign a new director
    • If succeeded, the Authorization committee begins distribution and promotion of the final documentary media, if requested by the Director

What is needed:

• Must make this concept LLC
• An extension to the WikiDot software to allow for polling, as per http://www.urbandictionary.com
• An implementation of the WikiDot application on a dedicated server, as according to http://www.wikidot.org/doc:installation#toc1
• A FAQ like http://www.wildsound-filmmaking-feedback-events.com/documentary.html

this is the main function (a poor copy&past&modify from PageLookupQModule….):

 class TagsLookupQModule extends QuickModule { public function process($data){ // does not use data $search = $_GET['q']; $siteId = $_GET['s']; if(!is_numeric($siteId)) return; if($search == null || strlen($search) ==0) return; $search1 = pg_escape_string(preg_quote($search)); $search2 = pg_escape_string($search); Database::init(); $q1 = "SELECT tag, tag_id FROM page_tag WHERE " . "tag ~* '^$search1' AND tag != '$search2' AND site_id = '$siteId'"; $q1 .= "ORDER BY tag LIMIT 20"; $q2 = "SELECT tag, user_id FROM page_tag WHERE " . "tag = '$search2' AND site_id ='$siteId'"; $db = Database::connection(); $result1 = $db->query($q1); $result1 = $result1->fetchAll(); $result2 = $db->query($q2); $result2 = $result2->fetchAll(); if($result1 == null && $result2 != null) $result = $result2; if($result2 == null && $result1 != null) $result = $result1; if($result1 != null && $result2 != null){ $result = array_merge($result2, $result1); } return array('tags' => $result); } } 

now I need to modify PageTagsModule.js in order to allow search operation.
anyone can help me? I think this feature would be very usefull for everyone.

thanks,
Gio

Thanks for sharing and using Wikidot!

1. su
2. su postgres
3. psql wd1
4. INSERT INTO user_settings (user_id) VALUES (1);

thanks Piotr!
Giovanni

you can do that by:

1. su
2. su postgres
3. psql wd1
4. UPDATE ozone_user SET super_admin = true WHERE unix_name = 'new-admin'

then start using the brand new admin.
Gio