If that URL would give an error, try this one:
https://github.com/ClassyBot/ClassicPress-v2-nightly/releases/download/2.0.0%2Bmigration.20240228/ClassicPress-nightly-2.0.0-migration.20240228.zip
An updated version of the Migration Plugin should be ready soon that will convert to ClassicPress v2.
A lot of work for sure, congratulations! I just got 2.0.0 with a new test site and it seems I lost my widget visibility functionality that I had with a theme. It did work in CP 1.7.3 and the older versions. As I’m not really a coder I can’t tell what’s going on.
Can you point me to the plugin that is not working?
It’s the Socrates Toolkit plugin, that comes with the Socrates premium themes. Up until now no problems in CP with them.
Sorry can’t help as it’s not a free plugin.
Have you tried to contact support?
Something that may be happening is CP v2 reports as WP v6, so plugins and themes may mistakenly read that as having block functionality, when CP does not. With CP v1, it reported as WP v4.9, so 3rd party add-ons would not try to enable block functions.
There are also other plugins that can manage widget visibility. If that’s all you need, it might be easiest just to change plugins.
Thanks Timkaye, that did the job!
I will contact the developer after the weekend anyway. Thanks for your suggestions!
Thanks very much for taking the time, Simone! In case of emergency you could have had my login details, but for now I have a solution.
I installed the public release version 2.0.0, but the Dutch translations are still being downloaded for 1.0.x - Dev. Several strings are now not being translated, such as the Previous and Next buttons.
I also noticed that “Discussion” has been translated to “Reacties”, not only is the translation plural instead of singular, but also incorrect. It should be “Discussie”. Because of this, there now seem to be two identical screen options. (See the enclosed screenshots).
Thanks for the report. Sorry about this.
Hi Tim,
Because I was curious, I took a look at the source code in /wp-admin/includes/translation-install.php. I noticed that the version /1.0.0/ is hardcoded on line 53.
As listed on Index of /v1/translations/core/1.0.0, these translations were last modified / updated on 21 November, 2023. Is that still the source?
I would really like to help out with the Dutch translations, but cannot find exactly were to do that.
Me thinks you are correct this are last sources uploaded. I am working with @MattyRob to get Crowdin all set and up to speed, will also check that hardcoded string to see if it’s better to make some amends to it. I personally would avoid hardcoded strings where possible but clearly Matt has the last word in it (there could be a reason for that in V1).
I am also working on an announcement and a tutorial to keep as reference for people who approach translating CP without prior knowledge of Crowdin.
Thanks for your help in localizing CP to Dutch!
The API server was rebuilt and migrated recently, the date on the translation zip files is when those files were uploaded to the new server. The last modified dates within the json file is a more accurate indication of the last time they were touched.
As Elisabetta has said, we are prioritising getting translation processes working on our side again. Hopefully that will be done very soon.
Ehm… I really hope that this is not true, because the dates in the JSON-file are much older.
nl_NL => 2019-03-06
pt_PT => 2019-03-27
ru_RU => 2019-01-29
All the others => 2018-12-20
@StonehengeCreations - those dates would indicate to me one of two things, either that id genuinely the last time the translation files were updated, or the dates were never changed with any update - either of those two are not good and I’m trying to work on a better solution going forwards. 
I would like to think that the dates were never updated, so the current dates would then be their initial release date. 
