[wiki] Textbook Upgraded

hakjoon · 2006-11-28 18:48:58

Textbook is now running the latest MediaWiki release.

Please let me know if you encounter any issues.

Thanks all, sorry this took longer then I expected.

Last edited by hakjoon (2006-11-28 18:49:10)

marios · 2006-11-28 19:20:16

Thanks hakjoon, I’ll be doing some work there these days.
I’ll let you know, if I see something.

regards, marios

Destry · 2006-11-29 21:01:57

Sorry, don’t have a robot…

Patrick, I don’t recall MW always having svn availability, but I’m working on another MW project and it works quite nice. Might look into that for the next upgrade.

I see you also were thinking sharp about safeguarding customizations and provided the .inc file. I’m guessing that was you. Nice trick. I’m going to use that if I need to, but I’m wondering, does one need to do that if they’re using subversion? I don’t think svn will overwrite anything. I haven’t really thought this all the way through yet so I could be off the mark here.

This page on configuration settings is extremely valuable. Here’s one that I never knew about before wgSkipSkins, which can make all our non-supported skin options disappear from user views. Adding this to LocalSettings.php should work nicely:

$wgSkipSkins = array("monobook", "chick", "cologneblue", "myskin", "nostalgia", "simple", "standard");

One thing I’m having trouble figuring out though is how to swap out the Monobook system messages for the custom TextBook skin.

Anyway, I’m hoping to slowly get back to working on the admin pages in the wiki again now that the backside of Txp has stabilized in appearance.

Last edited by Destry (2006-11-29 21:04:49)

hakjoon · 2006-11-29 21:56:04

Destry wrote:
Sorry, don’t have a robot…

What do you have against robots :)

Patrick, I don’t recall MW always having svn availability, but I’m working on another MW project and it works quite nice. Might look into that for the next upgrade.

In the end I’m not sure if that would really save me anything. I’d still have to export the release into it’s own folder and copy it over, it’s just as easy to just upload the zip.

I see you also were thinking sharp about safeguarding customizations and provided the .inc file. I’m guessing that was you. Nice trick. I’m going to use that if I need to, but I’m wondering, does one need to do that if they’re using subversion? I don’t think svn will overwrite anything. I haven’t really thought this all the way through yet so I could be off the mark here.

The reason I had to do this was because I cannot for the life of me get the upgrade scripts to run on Textdrive. Normally you just leave your LocalSettings file alone and just run the upgrade script. Since I can’t get the script to run I have to erase the LocalSettings file and run the installer again which creates a new Localsettings file. Since I’m not particularly good with copy and pasting between files in vi I figured it would just beeasier to put all the stuff we set in a file that won’t get messed with by MW.

Once I gave up on the upgrade script it works pretty well. I created a test folder and a test database to test the upgrades on before I run them on the actual install. That way it’s all tested in the same environment the upgrade will eventually run.

This page on configuration settings is extremely valuable. Here’s one that I never knew about before wgSkipSkins, which can make all our non-supported skin options disappear from user views. Adding this to LocalSettings.php should work nicely:

This seems like a nice addition since we don’t want people using the other skins.

One thing I’m having trouble figuring out though is how to swap out the Monobook system messages for the custom TextBook skin.

No idea on this one.

Destry · 2006-11-30 09:43:57

Nothing against robots (I read Asimov), just don’t have one.

hakjoon wrote:

In the end I’m not sure if that would really save me anything. I’d still have to export the release into it’s own folder and copy it over, it’s just as easy to just upload the zip.

Are you sure you have to export at all… why not just keep it under subversion? You won’t ever commit upstream of course, but that’s not an issue. Again, I might be missing something here, such as switching repos when the time comes for a new release, and whatnot. I’ll have to think about it more when I have time.

hakjoon · 2006-11-30 14:29:39

That can be done. We ran our servers at UVa as Working Copies from our subversion repository. You end up having .svn folders everywhere and it can cause some issues but for the most part it works. I like SVK a little better because it doesn’t leave the .svn folders everywhere, and you can use it with SVN repos no problem.

We’d have to remove the current wiki install and switch it over to a checkout because I don’t think there is a way to force SVN to checkout over an existing directory. Might be wrong here.

In the end I’m not sure. There is definitely an appeal to it, but we ran into some complications due to SVN at UVa that I’m not sure I want to commit to dealing with. We had a fairly complicated setup though, I have had zero issues running my TXP test installs off of SVN. I’m gonna have to think about this one.

marios · 2006-11-30 20:48:26

A small Issue that I came accross. The cross-langage inline-links for the Main Section pages.
I’m using the same Syntax as done for DE/EN.
( Using Uppercase short-language code for Greek with non ASCII characters in this case)
This doesn’t seem to produce working cross-language section links from the Lang-Box at the left, and the main Header doesn’t show up, just EL/

regards, marios

hakjoon · 2006-11-30 22:24:01

I have no idea why It’s doing that. everything seems right. I wonder if it’s something with how it’s encoding the title or something.

marios · 2006-11-30 23:18:20

Well, everything is in UTF-8, encoding, database-collation etc, so that shouldn’t be it.
Surprisingly switching from Greek to English works, but not the other way around for a Section Cross Link.
I gave it a try with some ASCII counterpart, but no luck.
The URL just won’t pop in, and no Section Header.

regards, marios

hakjoon · 2006-11-30 23:28:44

And if you add any other ones all end up on the same page because the title isn’t being passed through. This is perplexing

marios · 2006-11-30 23:55:25

I’ve been tinkering around with it.
The problem here, is, that the Section page had the following URL:
http://textpattern.net/wiki/index.php?title=Ξεκηνόντας_Δουλειά_με_το_Textpattern
But it should have this one
http://textpattern.net/wiki/index.php?title=El/Ξεκηνόντας_Δουλειά_με_το_Textpattern

Tried to change the URL, by moving page away and such, but it doesn’t fix the URL.

regards, marios

hakjoon · 2006-12-01 00:00:17

I think you can actually link it like this [[:el:page title]] notice the preceding colon. Although I think the sidebar is controlled by the [[el:page name]] links at the bottom of each page. I created a dummy page Intermediate Topics and it’s doing the same thing.

I’m having no luck finding anything on this, which is not unusual for mediawiki problems.

Textpattern CMS

Textpattern CMS support forum

#1 2006-11-28 18:48:58

[wiki] Textbook Upgraded

#2 2006-11-28 19:20:16

Re: [wiki] Textbook Upgraded

#3 2006-11-29 21:01:57

Re: [wiki] Textbook Upgraded

#4 2006-11-29 21:56:04

Re: [wiki] Textbook Upgraded

#5 2006-11-30 09:43:57

Re: [wiki] Textbook Upgraded

#6 2006-11-30 14:29:39

Re: [wiki] Textbook Upgraded

#7 2006-11-30 20:48:26

Re: [wiki] Textbook Upgraded

#8 2006-11-30 22:24:01

Re: [wiki] Textbook Upgraded

#9 2006-11-30 23:18:20

Re: [wiki] Textbook Upgraded

#10 2006-11-30 23:28:44

Re: [wiki] Textbook Upgraded

#11 2006-11-30 23:55:25

Re: [wiki] Textbook Upgraded

#12 2006-12-01 00:00:17

Re: [wiki] Textbook Upgraded

Board footer