New host for AviSynth

[Wilbert]

We finally have a new host: avisynth.nl!!!

The stuff on avisynth.org is still out there. If Richard comes here again I will ask him to hand over his domain.

The last few weeks i was busy moving all contents of avisynth.org to the new host. The translated sections should be the only ones which are not moved yet (will do that the coming weeks). So let me know when i forgot something else.

Much of the new wiki looks the same as the old one, but there is one thing which is different. I changed the user group rights in the following way

1. all:
   Everyone can read any page and create an account. In order to create an account you have to answer a question correctly (to keep the spammers out).
   
2. registered users:
   After creating an account you become a registered user, and you will be able to edit pages and change your user preferences. For the first ten edits you will need to answer a question again.
   
3. emailconfirmed users:
   When a user has his email address authenticated he/she will become an emailconfirmed user. You will be able to create and move pages and upload images in addition.
   
4. autoconfirmed users:
   After making ten edits you will be promoted to an autoconfirmed user and you can do the same as you could before but without answering any questions to edit a page.

Hopefully that will leave the spammers out. If not I will disable the account creation and let a few people do that for you.

If you have problems getting your emailaddress confirmed (I have read somewhere that an address with two dots will fail) or you have a problem with answering the questions drop me a pm.

If you want to help with the new wiki, the to do list can be found here: http://avisynth.nl/index.php/Avisynth_wiki:Current_events I asked WarpEnterprises to update the plugins. If anyone is interested, you can get my latest package (yes I know it's not complete): here (~345 MB). Let me know if you want ftp access.

[mariush]

Cool. Any reasons why you didn't use avisynth.net?

Unrelated... For me personally it will annoy me to no end to see that "index.php" in the urls. I'd change that to "pages" or something like that... you can do that easily with a plain entry in the virtual host configuration and some entries in localsettings.php of the wiki

$wgScriptPath = "/wiki"; // <--- folder where the mediawiki is on the server
$wgScriptExtension = ".php";
$wgArticlePath = "/pages/$1"; // <--- pages is what will show up in url
$wgUsePathInfo = true;

example of a virtual host on my dev server ... with mod_alias enabled outside in the modules list.

<VirtualHost *:80>
RewriteEngine On
ServerAdmin contact@example.org
DocumentRoot c:/projects/exampe
ServerName dev.example.org
# ServerAlias www.example.org
Alias /pages c:/projects/example/wiki/index.php
ErrorLog logs/examplewiki-error.log
CustomLog logs/examplewiki-access.log common

<Directory "c:/projects/example">
AllowOverride All
AddOutputFilterByType DEFLATE text/css text/js text/javascript application/javascript text/html
Order allow,deny
Allow from all
</Directory>

</VirtualHost>

[creaothceann]

Note that "rawsourceSeq_25_dll_20060412.7z" is a HTML error message and "tc2mp4_doom9dotorg_20070124.rar" is password-protected.

[Gavino]

Wilbert, thanks for your work on the new wiki (and your efforts on the previous one too).

I notice that the history of each page has been lost with the move, with only the latest version preserved. Is there any way it can be brought across too, as it's sometimes useful (especially for authors) to look back at the history of changes to a page?

[Forensic]

I just added a new example to (http://avisynth.nl/index.php/Overlay). This was my first time adding to the Wiki format and hope that I followed proper netiquette. It isn't much, but I want to walk before I run.

[kurish]

Three cheers, Wilbert. Thank you.

I bet you had a lot of other things you could've worked on, and this lurker appreciates your efforts. The wiki is a valuable resource; may it live long and prosper in its new home.

[Wilbert]

@mariush

I can't get that to work. I changed the following lines in LocalSettings.php:

$wgScriptPath = "";
$wgScriptExtension = ".php";

to

$wgScriptPath = "";
$wgScriptExtension = ".php";
$wgArticlePath = "/$1";
$wgUsePathInfo = true;

So pages should appear like

http://avisynth.nl/AviSource

instead of

http://avisynth.nl/index.php/AviSource

if i understand it correctly. But when uploading the modified LocalSettings.php it makes no difference. It doesn't recognize the first url.

@creaothceann,

Will look at it.

@Gavino,

Yes something went wrong. I guess i ticked the wrong box when exporting the pages and didn't check whether the history was included when importing the pages in the new wiki. It's too late now. I modified and updated several things after importing the pages and don't want to redo that again.

@Forensic,

Yes you did fine. Go ahead.

[Reel.Deel]

Hello everyone,

First of all, thanks Wilbert for all your efforts on preserving the AviSynth documentation. Kudos.

I recently changed the Deringing section to Deringing & Mosquito Noise in order to add MosquitoNR.
I know they're not the same, but since ringing and mosquito noise are often loosely associated with one another I though it would no problem to do this.
I think it's better than creating a separate section just for one plugin. I may be wrong so if anyone has a better idea please do say so.

[Wilbert]

Note that "rawsourceSeq_25_dll_20060412.7z" is a HTML error message and "tc2mp4_doom9dotorg_20070124.rar" is password-protected.

I didn't realise you got them from the zip-file. The first one can be obtained here. The password of the second one is doom9.org (see filename).

[StainlessS]

List of bad links in the AviSynth Filter Collection, here:
http://forum.doom9.org/showthread.ph...70#post1651270

LinkChecker v8.4 (v8.2 on sourceforge is bugged) here:-
http://wummel.github.io/linkchecker/

[Wilbert]

Something weird is happening on avisynth.nl.

Each time I edit a page (for example http://avisynth.nl/index.php/Convert), i don't see any content at all anymore. If you click on edit you will see it's still there, it's just not visible anymore ...

I never have seen this before, and i don't know what to do ...

http://avisynth.nl/index.php/Import empty too, what the hell?
http://avisynth.nl/index.php/Filter_SDK/Cplusplus_API ditto
http://avisynth.nl/index.php/Filter_SDK/avs2pcm
http://avisynth.nl/index.php/Filter_...g_instructions
http://avisynth.nl/index.php/Filter_...ler_optimizing
http://avisynth.nl/index.php/Filter_SDK/Ben_docs
http://avisynth.nl/index.php/Filter_SDK/Two-Five_SDK
http://avisynth.nl/index.php/Filter_SDK/SDK_license

[raffriff42]

I've been Googling - I think it's this reported bug:
[RESOLVED] No wiki rendered - text OK.
also here:
Manual: Errors and symptoms: All pages have no content, but when editing a page the wiki text is there

[foxyshadis]

Ah, so it may have had to do with recent server security updates bringing along a new PCRE.

[Reel.Deel]

Strange. I've done a few edits just a couple of days ago and did not encounter that problem. I hope this can be easily resolved (the external filters page is blank ).

Edit: I also see that the view counter at the bottom of the page is also gone.

[raffriff42]

Problem has spread to Main Page now...
You need to downgrade PCRE, or update MediaWiki to version 1.22.1 or newer

EDIT:
You're back! Hooray!

[Wilbert]

So i guess i need to update to version 1.22.1 (1.22.3?). I have no idea how to downgrade PCRE ... How do i find out which PCRE version I have, I didn't install it myself?

edit: it appears to work again, but i didn't do anything.

[foxyshadis]

It looks like it runs FreeBSD, so if you open a commandline, then:

pkg info pcre

will give you that info. Probably better to just update wiki before it happens again, though.

[Reel.Deel]

Wiki makeover? yay or nay? Just experimenting a little bit; would be nice to give the main page of the AviSynth Wiki an overdue makeover.

[Asmodian]

I like it.

It is better for high resolution displays. Though maybe keep the white lack of background?

[Wilbert]

The text is much too small for me (i'm looking at it on a widescreen laptop). Must be even worse on a non widescreen laptop/screen.
Sorry, i can't say it's an improvement.