El Alamein: Battles in North Africa, 1942 is one of the module pages on my list above of module pages which had problems converting. There’s nothing you can edit at the moment. I’m dealing now with problems which prevent that.
In the meantime, the first step for fixing your page is to clearly state what’s wrong with it, in comparison with the old module page.
PMing me the details of what should go where is likely the simplest way.
Got it. Once I’m able to create new projects, I’ll create 3 new ones and set up their skeletons, then PM you about which specific module files go where.
I’m not getting the information I need for troubleshooting in the logs at the moment. That’s what I’ll be tackling on Sunday.
When you create a project, you should now be redirected to the newly created project page. If this doesn’t work for you, please let me know and provide details of what you did so I can investigate further.
From https://vassalengine.org/library/new I tried to make a new Project named “Afrika Korps” (and “Afrika Korps by Christian Holm Christensen”) which gave the error
APIError: 401 Unauthorized: Unauthorized
(around 18:20 CEST)
Didn’t work despite several refresh etc.
Yours,
Christian
I get the same Unauthorized error when I try to edit a project I am the owner of. (Specifically, Stalingrad Roads: Battle on the Edge of the Abyss).
Perhaps it’s “in the works”, but there should be an easy-to-find upload link for members so inclined to start projects. Might be nice if it found its way into the icon bar at top left, rather than at the bottom of the page, hidden from view. There’s an opportunity here!!
Would you elaborate on this a bit? Maybe provide a screenshot of what you mean. There’s no upload link I know of at the bottom of any page.
It seems fairly obvious they mean that there should be a link (there currently isn’t) and that it shouldn’t be a small one at the bottom left of the page (as it was previously).
I know the immediate cause of this now: It’s because the POST that the frontend sends to do the upload is receiving this back as a response:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Bad Gateway</title>
</head><body>
<h1>Bad Gateway</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
</p>
</body></html>
I don’t know why yet.
Oh! In the old library! Thanks for that context. I had forgotten that there was an item for uploading files in the Tools dropdown—I’ve uploaded a file that way maybe once or twice in a dozen years.
In the new library, each release has its own file upload link. I.e., you will find the file upload link in the place where the file you intend to upload will go.
Thanks. I do hope the current situation, where there appears to be no link to create a new project on the module page or anywhere else, is not final.
(But maybe that’s for best right now, as creating new projects seems to be impossible anyway)
Just tried to upload a minor change that I made to an extension and got the following error:
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
The file I tried to upload was named: 6._Combat_Commander_-_Resistance-2.6.4.vmdx
I randomly pulled one of the other CC:Europe extensions and the file name formatting is similar. Oddly, however, while all the other CC:Europe extensions are there, the Resistance extension is not (neither in the current or older versions).
I’m just speculating, so I may be way-off: Could it have something to do with a cross-domain request in uploadFile and the back-end server isn’t set up for that? If you do development on same-server or the like, you may not see that problem.
Other problems could be mis-configuration of port numbers.
Seems like the same error as the one Joel found the proximate cause for.
Yours,
Christian
I think it’s not to do with CORS, as the backend does handle CORS.
My suspicion is that there’s a problem with the temporary upload directory; it’s surprising that a problem there would be returned as a 502 (by the proxy!) instead of a 500.
The problem you’re having with creating that project is that the project name doesn’t match the regex ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$. I.e., it has to be alphanumeric, hyphens, or underscores, and no more than 63 characters long.
I am having account access issues with the new library.
For context: I have been doing updates of published modules in the Operational Combat Series (OCS), Line of Battle (LoB) & and its predecessor Regimental Sub-Series (RSS).
My user name if fumanpo (which can be found in uploaded modules in all the pages of all games in the series above. Right now I only see that account listed in 1-2 of the needed pages.
Some of the others have another account name ‘Herman_Wu’ which is either old or created by someone else…I can’t access that account at all with my usual usernames or passwords.
Can my most current account name ‘fumanpo’ be added to all the modules in question? Thanks.
I stumbled across this thread only today. I find I am responsible for many new projects because I authored pages in the vassalengine.org/wiki. That is ok for me, but I suspect many other authors will be in the place I was yesterday, ignorant of the change, unaware of the implied responsibilities, and wondering why they can no longer edit some wiki pages.
Would it be possible to send an email to everyone whose pages are affected by this change? (Maybe there was one and I’ve missed it!) I say email, because I didn’t spend time in this discussion place before today.
Is it intended that pages in the old wiki that are not modules are still editable? It looks like they are. Is moderation of such edits still happening?
I have done a lot of work on the GDW/GRD/HMS Europa series of games. Should there be a high level “Project” for the whole series, with links to all the relevant related “Projects”?
I too have tried creating such a new project with Module Library - Vassal and get the APIError: 400 Bad Request: Invalid project name against the name Europa Series. No strange characters in that name.