Hi there,
Martin, Bryce and Travis from our friendly hosters at OSUOSL have worked on switching the inkscape.org website to the newer version this evening.
In some parts of the world, due to DNS propagation, you might not yet see the new page, but you will soon (it looks pretty much the same, though, just the backend is newer).
It now features a new shiny django (yay!).
Unfortunately, it currently has problems with page edits, news edits and resource uploads.
Please hold off editing anything on it, to not lose any work.
Martin is working on fixing things, and will let you know when it's good for editing again.
Downloads and viewing the pages work as usual (except for viewing pasted texts), so most people won't be affected by the issues.
Kind Regards, Maren
Thanks for the update!
It looks like messaging is missing (little envelope icon is gone). Just fyi (I check mine quite often, as I use it for moderation).
Thanks again, brynn
-----Original Message----- From: Maren Hachmann Sent: Thursday, October 11, 2018 7:14 PM To: Inkscape Devel List ; translators ; Inkscape-Docs Subject: [Inkscape-devel] Website update: current status
Hi there,
Martin, Bryce and Travis from our friendly hosters at OSUOSL have worked on switching the inkscape.org website to the newer version this evening.
In some parts of the world, due to DNS propagation, you might not yet see the new page, but you will soon (it looks pretty much the same, though, just the backend is newer).
It now features a new shiny django (yay!).
Unfortunately, it currently has problems with page edits, news edits and resource uploads.
Please hold off editing anything on it, to not lose any work.
Martin is working on fixing things, and will let you know when it's good for editing again.
Downloads and viewing the pages work as usual (except for viewing pasted texts), so most people won't be affected by the issues.
Kind Regards, Maren
_______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi,
another status update:
Martin has worked to fix the issues that had the greatest impact on website use, after the switch to the new Python 3 version of the website.
What works again: -----------------
- News editing and translation - CMS page editing and publishing - Registration - Uploading images
What doesn't work: ------------------
- Correct menu language (when you visit the website, you may get English pages, but see a menu in German, Italian, or some other language. This doesn't happen consistently.) - Providing fallback pages if a page doesn't exist in a certain language (it then just goes directly to the English page, with the - hopefully - English menu).
This means that translators must pay extra attention on the URL, to see if they are working on their own language, and not the English page!
- Messages between users - ... and some more, see https://gitlab.com/inkscape/inkscape-web/issues
What works differently: -----------------------
The website does no longer use link plugins. Those were a source of a lot of issues, confusing editors and the CMS alike. Martin converted all existing link plugins to normal html links.
This means that - unless a Table of contents, an image, a gallery, a user list or any other plugin are part of the page - one can now copy-paste almost any text from one page to another, without risking to break something.
All new links will now be inserted using the link icon in the editor (or <a href="">....</a> in the source mode). As redirects aren't working properly, you need to include the language code for the language you're linking to in the link.
For a link that is goes to another page on inkscape.org, do not include the domain. In the protocol dropdown, select '<other>' instead of 'https' to be able to leave it out.
Another side effect of the change seems to be that publishing works a lot faster than we're used to.
The Website instructions Wiki page has been updated to reflect the current changes: http://wiki.inkscape.org/wiki/index.php/WebSite
Help needed -----------
Martin has asked me to ask if someone (preferably someone who is fluent in Python, and if possible, has Django experience) can help with website bug fixing. A good place to start would be to install the website locally on your computer (requires Linux, or a VM with Linux), and to check on the issues section for the website on gitlab.
Vectors team, could you publish this request on social media? Ask Martin for details :)
Maren
Am 12.10.18 um 03:14 schrieb Maren Hachmann:
Hi there,
Martin, Bryce and Travis from our friendly hosters at OSUOSL have worked on switching the inkscape.org website to the newer version this evening.
In some parts of the world, due to DNS propagation, you might not yet see the new page, but you will soon (it looks pretty much the same, though, just the backend is newer).
It now features a new shiny django (yay!).
Unfortunately, it currently has problems with page edits, news edits and resource uploads.
Please hold off editing anything on it, to not lose any work.
Martin is working on fixing things, and will let you know when it's good for editing again.
Downloads and viewing the pages work as usual (except for viewing pasted texts), so most people won't be affected by the issues.
Kind Regards, Maren
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Thanks for the update, Maren. And thanks - As Always - for your hard work on the website, Martin! And of course thanks to everyone else who pitches in!
I just wanted to make one note. And ask a question.
It is possible to send messages.....by which I mean that it appears that a message is sent. However, there's no way to receive messages. There's no access to inboxes.
I actually had sent 2 or 3 messages (moderation issues) before I realized that we can't access our inboxes. Will those members eventually receive them? Or should I plan to re-send them later?
Thanks again! brynn
-----Original Message----- From: Maren Hachmann Sent: Friday, November 02, 2018 5:14 PM To: Inkscape Devel List ; translators ; Inkscape-Docs Subject: [Inkscape-docs] [Inkscape-devel] Website update: current status
Hi,
another status update:
Martin has worked to fix the issues that had the greatest impact on website use, after the switch to the new Python 3 version of the website.
What works again: -----------------
- News editing and translation - CMS page editing and publishing - Registration - Uploading images
What doesn't work: ------------------
- Correct menu language (when you visit the website, you may get English pages, but see a menu in German, Italian, or some other language. This doesn't happen consistently.) - Providing fallback pages if a page doesn't exist in a certain language (it then just goes directly to the English page, with the - hopefully - English menu).
This means that translators must pay extra attention on the URL, to see if they are working on their own language, and not the English page!
- Messages between users - ... and some more, see https://gitlab.com/inkscape/inkscape-web/issues
What works differently: -----------------------
The website does no longer use link plugins. Those were a source of a lot of issues, confusing editors and the CMS alike. Martin converted all existing link plugins to normal html links.
This means that - unless a Table of contents, an image, a gallery, a user list or any other plugin are part of the page - one can now copy-paste almost any text from one page to another, without risking to break something.
All new links will now be inserted using the link icon in the editor (or <a href="">....</a> in the source mode). As redirects aren't working properly, you need to include the language code for the language you're linking to in the link.
For a link that is goes to another page on inkscape.org, do not include the domain. In the protocol dropdown, select '<other>' instead of 'https' to be able to leave it out.
Another side effect of the change seems to be that publishing works a lot faster than we're used to.
The Website instructions Wiki page has been updated to reflect the current changes: http://wiki.inkscape.org/wiki/index.php/WebSite
Help needed -----------
Martin has asked me to ask if someone (preferably someone who is fluent in Python, and if possible, has Django experience) can help with website bug fixing. A good place to start would be to install the website locally on your computer (requires Linux, or a VM with Linux), and to check on the issues section for the website on gitlab.
Vectors team, could you publish this request on social media? Ask Martin for details :)
Maren
Am 12.10.18 um 03:14 schrieb Maren Hachmann:
Hi there,
Martin, Bryce and Travis from our friendly hosters at OSUOSL have worked on switching the inkscape.org website to the newer version this evening.
In some parts of the world, due to DNS propagation, you might not yet see the new page, but you will soon (it looks pretty much the same, though, just the backend is newer).
It now features a new shiny django (yay!).
Unfortunately, it currently has problems with page edits, news edits and resource uploads.
Please hold off editing anything on it, to not lose any work.
Martin is working on fixing things, and will let you know when it's good for editing again.
Downloads and viewing the pages work as usual (except for viewing pasted texts), so most people won't be affected by the issues.
Kind Regards, Maren
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
_______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs
Oops. Sorry, I have a couple more questions.
1 -- I don't understand what this means:
As redirects aren't working
properly, you need to include the language code for the language you're linking to in the link.
Is that something which translators need to understand? If it's for everyone, what is meant by "redirect" in this context?
2 -- About links to another page on the website:
For a link that is goes to another page on inkscape.org, do not include
the domain. In the protocol dropdown, select '<other>' instead of 'https' to be able to leave it out.
Perhaps "<other>" was chosen because of its width? But I wonder if "inkscape.org" or something else more specific might reduce confusion? I'm just thinking for myself, if it happens I don't make any edits for a few months, I'll forget that I'm supposed to use <other> for local links.
Hhmm.... Ok, I'm working on adding a new FAQ, and trying to make a link to the Community page. I choose <other> and then I paste in the URL. But the protocol switches itself to https://, and the https:// is removed from the URL. But the domain is still there.
I can switch it back to <other>. But should the URL field just say "community/" ? Or should it be "/community/" ? It looks like "/community/" is the right answer. I'll try to publish..... Ok, it looks like that worked :-)
Thank you very much, brynn
-----Original Message----- From: Maren Hachmann Sent: Friday, November 02, 2018 5:14 PM To: Inkscape Devel List ; translators ; Inkscape-Docs Subject: [Inkscape-docs] [Inkscape-devel] Website update: current status
Hi,
another status update:
Martin has worked to fix the issues that had the greatest impact on website use, after the switch to the new Python 3 version of the website.
What works again: -----------------
- News editing and translation - CMS page editing and publishing - Registration - Uploading images
What doesn't work: ------------------
- Correct menu language (when you visit the website, you may get English pages, but see a menu in German, Italian, or some other language. This doesn't happen consistently.) - Providing fallback pages if a page doesn't exist in a certain language (it then just goes directly to the English page, with the - hopefully - English menu).
This means that translators must pay extra attention on the URL, to see if they are working on their own language, and not the English page!
- Messages between users - ... and some more, see https://gitlab.com/inkscape/inkscape-web/issues
What works differently: -----------------------
The website does no longer use link plugins. Those were a source of a lot of issues, confusing editors and the CMS alike. Martin converted all existing link plugins to normal html links.
This means that - unless a Table of contents, an image, a gallery, a user list or any other plugin are part of the page - one can now copy-paste almost any text from one page to another, without risking to break something.
All new links will now be inserted using the link icon in the editor (or <a href="">....</a> in the source mode). As redirects aren't working properly, you need to include the language code for the language you're linking to in the link.
For a link that is goes to another page on inkscape.org, do not include the domain. In the protocol dropdown, select '<other>' instead of 'https' to be able to leave it out.
Another side effect of the change seems to be that publishing works a lot faster than we're used to.
The Website instructions Wiki page has been updated to reflect the current changes: http://wiki.inkscape.org/wiki/index.php/WebSite
Help needed -----------
Martin has asked me to ask if someone (preferably someone who is fluent in Python, and if possible, has Django experience) can help with website bug fixing. A good place to start would be to install the website locally on your computer (requires Linux, or a VM with Linux), and to check on the issues section for the website on gitlab.
Vectors team, could you publish this request on social media? Ask Martin for details :)
Maren
Am 06.11.18 um 04:19 schrieb brynn:
Oops. Sorry, I have a couple more questions.
1 -- I don't understand what this means:
As redirects aren't working
properly, you need to include the language code for the language you're linking to in the link.
Is that something which translators need to understand?
- Yes, you probably won't need to worry about this.
If it's for everyone, what is meant by "redirect" in this context?
2 -- About links to another page on the website:
For a link that is goes to another page on inkscape.org, do not include
the domain. In the protocol dropdown, select '<other>' instead of 'https' to be able to leave it out.
Perhaps "<other>" was chosen because of its width? But I wonder if "inkscape.org" or something else more specific might reduce confusion? I'm just thinking for myself, if it happens I don't make any edits for a few months, I'll forget that I'm supposed to use <other> for local links.
- In a few months (or maybe earlier), we will have an automatted search mask for internal links. Please try to remember it until then.
See https://gitlab.com/inkscape/inkscape-web/issues/238 for updates.
Hhmm.... Ok, I'm working on adding a new FAQ, and trying to make a link to the Community page. I choose <other> and then I paste in the URL. But the protocol switches itself to https://, and the https:// is removed from the URL. But the domain is still there.
I can switch it back to <other>. But should the URL field just say "community/" ? Or should it be "/community/" ? It looks like "/community/" is the right answer. I'll try to publish..... Ok, it looks like that worked :-)
- Yes, see also the linked Wiki page below where it is explained in detail. Specifically, you will find the relevant section at http://wiki.inkscape.org/wiki/index.php/WebSite#Specific_Instructions
Maren
Thank you very much, brynn
-----Original Message----- From: Maren Hachmann Sent: Friday, November 02, 2018 5:14 PM To: Inkscape Devel List ; translators ; Inkscape-Docs Subject: [Inkscape-docs] [Inkscape-devel] Website update: current status
Hi,
another status update:
Martin has worked to fix the issues that had the greatest impact on website use, after the switch to the new Python 3 version of the website.
What works again:
- News editing and translation
- CMS page editing and publishing
- Registration
- Uploading images
What doesn't work:
- Correct menu language (when you visit the website, you may get English
pages, but see a menu in German, Italian, or some other language. This doesn't happen consistently.)
- Providing fallback pages if a page doesn't exist in a certain language
(it then just goes directly to the English page, with the - hopefully - English menu).
This means that translators must pay extra attention on the URL, to see if they are working on their own language, and not the English page!
- Messages between users
- ... and some more, see https://gitlab.com/inkscape/inkscape-web/issues
What works differently:
The website does no longer use link plugins. Those were a source of a lot of issues, confusing editors and the CMS alike. Martin converted all existing link plugins to normal html links.
This means that - unless a Table of contents, an image, a gallery, a user list or any other plugin are part of the page - one can now copy-paste almost any text from one page to another, without risking to break something.
All new links will now be inserted using the link icon in the editor (or <a href="">....</a> in the source mode). As redirects aren't working properly, you need to include the language code for the language you're linking to in the link.
For a link that is goes to another page on inkscape.org, do not include the domain. In the protocol dropdown, select '<other>' instead of 'https' to be able to leave it out.
Another side effect of the change seems to be that publishing works a lot faster than we're used to.
The Website instructions Wiki page has been updated to reflect the current changes: http://wiki.inkscape.org/wiki/index.php/WebSite
Help needed
Martin has asked me to ask if someone (preferably someone who is fluent in Python, and if possible, has Django experience) can help with website bug fixing. A good place to start would be to install the website locally on your computer (requires Linux, or a VM with Linux), and to check on the issues section for the website on gitlab.
Vectors team, could you publish this request on social media? Ask Martin for details :)
Maren
participants (2)
-
brynn -
Maren Hachmann