[e-lang] It the wiki.erights.org new account creation broken?

[James Graves]

Speaking of which, I just when through the create account flow on
submitting my username/password/other-credentials, I get a blank page.
I received no email, and when I try to log in it says there is no
such username.

Could you look into this?

I tried to create an account with an email address and it failed. I
saw the blank page too and it just sat there.

Generally, email is broken on this machine and has been for a long
time because of issues with setting up an SMTP server on that
particular box... but that's a discussion for another day.

At any rate, I was able to create an account without putting in an
email address, and that did work.

For now if you need a password reset, just contact me directly.

When we finish getting the new server going, with a new version of
MediaWiki, we'll revisit this and the other longstanding issues such
as spam supression.

As a very quick hack, I'll just take out the email field of the
account creation form.

James Graves

[Kevin Reid]

James,

While you're reworking the wiki server, please make sure that these
features are enabled:

* MediaWiki API, so that it is possible to programmatically download
the contents of a category (for spec-test-suite purposes).

* The #if parser function, so that the {{msg}} template can have the
convenient syntax I want.

[Nathan]

James,

Thanks for describing the cause. I created an account without an
email field and updated the list of language implementations to add
eonhs here:

http://wiki.erights.org/wiki/Object-capability_languages

I also updated the eonhs wiki to point back to that link as well as
Kevin's separate E-on-Haskell codebase.

Post by Kevin Reid
James,
While you're reworking the wiki server, please make sure that these
* MediaWiki API, so that it is possible to programmatically download
the contents of a category (for spec-test-suite purposes).

+1

We want the code snippets that user browse to be identical to those
which are automatically tested by implementations, so any streamlining
of the synchronization between wiki and automated tests is quite
useful.

For now I am quite content to have a manual code review process
between fetching snippets and executing tests in order to catch
attempted security compromises. In other words I don't want to block
automated testing on strong automated confinement, but I also don't
want out-of-date examples. :-)

[...]

Post by Kevin Reid
--
Kevin Reid                                  <http://switchb.org/kpreid/>

[...]

Regards,
Nathan

[James Graves]

Post by Kevin Reid
While you're reworking the wiki server, please make sure that these
* MediaWiki API, so that it is possible to programmatically download
the contents of a category (for spec-test-suite purposes).
* The #if parser function, so that the {{msg}} template can have the
convenient syntax I want.

Noted.

I don't have an accurate ETA for the new server and other transitional
shenanigans, but it should be less than 2 months. I'll try to give as
much notice for downtime as I can.

James Graves

[Kevin Reid]

Post by James Graves

Post by Kevin Reid
While you're reworking the wiki server, please make sure that these
* MediaWiki API, so that it is possible to programmatically download
the contents of a category (for spec-test-suite purposes).
* The #if parser function, so that the {{msg}} template can have the
convenient syntax I want.

Noted.
I don't have an accurate ETA for the new server and other transitional
shenanigans, but it should be less than 2 months. I'll try to give as
much notice for downtime as I can.

Ping.

[James Graves]

Hi All,

My oh my, how the time flies!

Well, at least the new server is up and running, and stable. It has
RAID, and a slightly faster processor. We just need to scare up an
extra UPS for it.

The next steps are:

0. Check that backups are running OK.

1. Check to see that MySQL is set up correctly on the new server.

2. Try to export the existing MediaWiki contents.

3, Import the contents into the new system. (Hopefully there won't be
issues like we have to convert the data in some intermediate steps.)

4. Make an announcement, and let people try it out.

5. If things look good, freeze the existing wiki, and do the final
export / import.

6. Go live with the new IP address (will require a DNS change).

I'll let you all know when we can try out the test version.

BR,

James