Switching to the New Module Library

[Segmelo]

• I can’t delete anything that was incorrectly inserted
• I can’t upload a module (APIError: 400 Bad Request: unexpected end of input while parsing minor version number)
• In fact, you can’t edit almost anything

[uckelman]

@Segmelo

• I can’t delete anything that was incorrectly inserted

Would you show me an example of this?

@Segmelo

• I can’t upload a module (APIError: 400 Bad Request: unexpected end of input while parsing minor version number)
• In fact, you can’t edit almost anything

These are expected at the moment.

[fumanpo]

That seems to have done the trick…thanks.

[uckelman]

You should get a slightly better error message now when trying to add a release with a malformed version number.

[uckelman]

How soon are people getting a 401 Unauthorized error after logging in?

[Segmelo]

I included a wrong item in the packages section and I can’t remove it

[uckelman]

What’s wrong with it?

[Segmelo]

I can remove Cingapura-Somnium. Its not a module.

And taking advantage of this, I’ve already tried all the ways to name my module and none of them are accepted, always with the same error “APIError: 400 Bad Request: unexpected end of input while parsing minor version number”

[uckelman]

@Segmelo

I’ve already tried all the ways to name my module and none of them are accepted, always with the same error “APIError: 400 Bad Request: unexpected end of input while parsing minor version number”

What is the version number defined in the module?

[Segmelo]

The module version is 1.0

[uckelman]

@Segmelo

The module version is 1.0

1.0 isn’t a valid version number. See below:

@uckelman

On upload, module versions are are checked that they conform to the version scheme laid out by Semantic Versioning. The gloss is that versions have to be of the form x.y.z, with optional trailing pre-release and build identifiers.

If this is a new release, you should change the version number to 1.0.0. If you’re trying to upload a file that was on an old module page but didn’t get moved properly, ask me to move it instead of uploading the file again.

[Segmelo]

OK, it worked

another issue. The old modules were published in the wiki by their name and in the transfer, the new modules are with a number and not by their name. How to change this?

[uckelman]

Which module is this?

[Segmelo]

For example, Module Library - Vassal

But the name of project is Cherburg of Somnium

[cpcunningham]

Uploading an newer module for Imperial Tide. Anything I’m missing or adding to get this SyntaxError?

Cavan

[uckelman]

No, there’s nothing you can do at the moment to make it work.

[uckelman]

@Segmelo

For example, Module Library - Vassal

But the name of project is Cherburg of Somnium

I don’t understand what problem you’re pointing out. I see both releases of the module on the old and new pages:

Old:

New:

[jrwatts]

I had to log out and back in about 14 hours ago because I started getting 401 errors on edit, then just now, I had to do it again. Since I have 2FA turned on, this is getting annoying…

[Benkyo]

Any “package” you create or misname cannot be deleted or renamed: this is the problem being described.

[uckelman]

I’m at a complete loss here. I need it stated explicitly what’s wrong.