Third retrieve is proceeding (slowly), and in ~4 days it should be finished. At that time (before running html processing for all pages) I need feedback about suggestion in T48096#594983 by @nBurn (nBurn) to change warning text (and add link to an explanatory page). @Inês Almeida (brita_), @Francesco Siddi (fsiddi), @Aaron Carlisle (Blendify), anyone: do you agree? What URL to add for explanatory page? Some page in new wiki? Or better to leave warning as it is now?

It looks like old Mediawiki doesn't want to work nicely with php7. Also there's no guarantee that the result will look anything like the current one, so I guess its gonna be a new 10 d crawl..

Hi, I'm now contemplating to do another full retrieve, so this would be a perfect time to make decisions about suggestions from @nBurn (nBurn) in T48096#594983. Anyone else also want those changes?

Thanks for the patch, but I don't think the intent of the original task was to add prefixes for In/Out. that should already be clear from the UI and not cause any problems in the Python API. Rather it was to rename to "Vector1" and "Vector2" for example.

Yes, the only special pages currently included are the edit and history pages. Technically, all those specials (non-existing parent page, what links here, recent user contributions for User:X pages) can be added, if someone else also seconds this motion? "What links here" and "recent user contributions" could be retrieved to e.g. links.html and contributions.html located under page folders. I don't think they would add too much to archive size, it would just take me time to do it.

There seems to be some weirdness going on if wiki user's created subpages without a base page.

I would keep all the deleted pages and their redirects. This would avoid broken links.

I would keep all the deleted pages and their redirects. This would avoid broken links.
I don't think that the asccii character issue is is a good compromise as this will result in broken links? Or maybe I misunderstood something.

I believe this is a bug and unless use_property_split should not be used in certain situations. If that is the case the documentation should reflect this.

Ok, new version of archived wiki is available temporarily for review at http://tkeskita.kapsi.fi/temp/en.blender.org/

• Page list available in text and html formats. Pages now include also deleted pages and redirections to deleted pages. Page count is 53173 out of 53221, so almost everything seems to be included.
• Includes index.html, edit.html and history.html pages for each wiki page. History page lists date and username of 50 latest edits.
• Page names may contain underscores instead of spaces, and they should both be found. This was done by creating directory symlinks like "Release_Notes" that point to "Release Notes". Is this OK?
• All links to en.blender.org in pages have been converted into relative paths, so this can be freely placed in any directory and links should work. Since the whole script size is now 350 lines, the current bash script is attached here:

Agree, I wouldn't worry too much about fixing every broken link. It's nice if it doesn't take too much time, but for an archived website it's ok if only the basics are functional.

I wouldn't worry about saving the full edit history. I'm not sure how you could preserve that without a significant increase to the total size and file count of the wiki archive. It might be helpful to see who the last 50 or 100 people that edited the page are (and maybe the first 50 edits), but if someone needed more info than that they could download the wiki data dump.

I've been wondering about history pages. After pages are static it will not be possible to do comparisons between versions, so you will only see who edited the page last and when. Is it still interesting to save history page? @Inês Almeida (brita_)?

In T48096#586329, @Tuomo Keskitalo (tkeskita) wrote:

In T48096#585785, @LazyDodo (LazyDodo) wrote:

I was browsing the scraped copy last week, and bumped into a searchbox somewhere, we'd probably have to get rid of those otherwise users will use them and make tickets that it is not working.

I guess you mean the quick search on lower left corner? Good idea! I'll also remove the "Page" menu from top right and "Wiki" menu from bottom right.

In T48096#585634, @Tuomo Keskitalo (tkeskita) wrote:

1. The old wiki contains deleted pages, such as this, which redirects to here which is deleted. wget does not want to download such pages. Is it OK to leave these pages out, or should I try to find some way to get also them in? My script is collecting a list of these failed pages, let's see how long it gets.

In T48096#585785, @LazyDodo (LazyDodo) wrote:

I was browsing the scraped copy last week, and bumped into a searchbox somewhere, we'd probably have to get rid of those otherwise users will use them and make tickets that it is not working.

Understood. I've created a post on Right-Click Select: post

It's a good suggestion, but we don't handle this kind of usability suggestion in the bug tracker.
https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

I was browsing the scraped copy last week, and bumped into a searchbox somewhere, we'd probably have to get rid of those otherwise users will use them and make tickets that it is not working.

In T48096#585634, @Tuomo Keskitalo (tkeskita) wrote:

4. @Dan McGrath (dmcgrath) : My script has stopped running a few times, wget says "Unable to establish SSL connection." When I try to continue, the page is loaded without errors. Any ideas what is causing this? I'm not choking the server, am I?

@blend-it (blend-it) vorrei dare una mano nelle traduzioni e con il manuale in italiano..
piccoli compiti da eseguire..

1. The old wiki contains deleted pages, such as this, which redirects to here which is deleted. wget does not want to download such pages. Is it OK to leave these pages out, or should I try to find some way to get also them in? My script is collecting a list of these failed pages, let's see how long it gets.
2. The old wiki contains pages with non-ascii characters in their page names, which at least my ext4 filesystem does not like to use correctly as directory name, such as this. I'm gonna convert all special characters in page names into %XX hexadecimal representation, using wget option --restrict-file-names=ascii. That way the pages will at least be downloaded, but I think they will not be found if you just try to access the static wiki like this, instead they would be accessible like this which makes it impossible to read. This affects only the page name, the page contents is still intact. Is this compromise acceptable? This affects only non-english pages.
3. Just realized that the static wiki URL for "Page" would be "https://archive.blender.org/wiki/index.php/Page, so the base path is /wiki/index.php and not just /wiki. Is that OK?
4. @Dan McGrath (dmcgrath) : My script has stopped running a few times, wget says "Unable to establish SSL connection." When I try to continue, the page is loaded without errors. Any ideas what is causing this? I'm not choking the server, am I?

In T48096#577069, @Benjamin Humpherys (brhumphe) wrote:

Does the wiki log whenever someone tries to visit a missing page? That would be a good way to identify broken links.

@Benjamin Humpherys (brhumphe) I don't know about mediawiki, but at least www server logs errors. Good idea to use those to make the final check, when I get there!

@Sergey Sharybin (sergey) why do you think the licensing rule is strict?
A public domain diagram of an algorithm can be uploaded with its original license and author if needed. I think public domain, other versions of CC and the licenses used in the previous Blender wiki are all perfectly fine.
The Blender Cloud says: "Unless notified otherwise, all digital content (webpages, video, artwork, 3D data) is available under the Creative Commons Attribution 4.0.". Blender Cloud textures are CC0. So these can also be uploaded with their original license.

@Inês Almeida (brita_), i am all for keeping things locally in terms where they belong to. Makes it easier to version, control consistency, and see where they actually are supposed to be put.

I am very sorry to hear this. I am also sorry that I took over a week replying.
Please don't be discouraged by feedback or by people disagreeing, it only means that people care.
Specially with text, there can be endless discussions about wording and commas which can be frustrating.
Maybe you picked controversial topics? Can you give a second try to writing new content? With 2.8 there are exciting new opportunities to write entirely new chapters about Grease Pencil Object layers, groups and visibility.
The Blender documentation needs *you* :)

It's been some time without a reply.
@Sergey Sharybin (sergey) @Campbell Barton (campbellbarton) do you have anything against putting media files in the manual SVN under a new files/ folder in the root directory?

thanks for your comment! Yes I abandoned my remaining few open tasks related to Blender Manual. My work during last month on Blender Manual has received mostly negative feedback and only few positive comments. I concluded that it is best for me to work on something else.

In T51172#577175, @Tobias Heinke (TobiasH) wrote:

Yeah sure, except for "incrementally make changes" it's doesn't works and likely ends up in a mess.

@Tuomo Keskitalo (tkeskita) I tend to agree with the other comments.
Updating the manual to 2.8 is already a huge task and I don't think it's very realistic to restructure it at the same time.
It would already be wonderful if you would pick up one section for something that is new or completely changed and make sure that's well documented.
Try the grease pencil! This is a very popular area that people are beginning to experiment with, including people who are totally new to Blender. It would be great to have official docs for it and a list of handpicked video tutorials to see different workflows and what can be achieved.

Hey @Aaron Carlisle (Blendify) can this be closed?

Hi @Tuomo Keskitalo (tkeskita) you seemed to have abandoned the revisions to improve the clarity of the rules for writing the Blender Manual.
Is there a problem? It think it was a really good effort!

@Aaron Carlisle (Blendify) : I don't know exactly how documentation repo is managed. Can you please review this documentation page for glTF importer/exporter?
Is it possible to have commit access on the repo to be able to update this page later ?