- User Since
- May 8 2008, 3:11 PM (674 w, 6 d)
Thu, Mar 18
A redirect was added to map /tutorials to /support/tutorials. Thanks for the report!
Mar 3 2021
Feb 23 2021
Unfortunately we are not allowed to do wildcard DNS with our provider:
Feb 10 2021
Dec 9 2020
Nov 12 2020
Test comment for mail spot check
Nov 5 2020
Closing test task
Oct 29 2020
It appears fine for me, and some others, but some of the web devs also were able to verify some issues where it would play directly by URL but not in the player.
Oct 23 2020
Oct 13 2020
It's a known limitation of the current setup. At some point it will be addressed, but ty for reporting it.
Jun 5 2020
Ah never mind, it looked like @Francesco Siddi (fsiddi) disabled the mirrors about an hour ago or so. Seems it is a known issue! Thanks for reporting.
I checked the www mirror site, and Clarkson is listed as disabled. I don't know at this very second if it was just disabled by someone and our packets are crossing each other in the sky, but I am curious if maybe you just had an out of date mirror URL? I assume you got this URL from blender.org itself?
Try our download site. Seems they are offline atm (no pings, can't even reach the base site.
Feb 20 2020
Feb 19 2020
I took a look, and it appears that mod_rewrite stuff should be part of the FileInfo override that we already have in place. So you should be able to patch stuff up in the commits as well.
I supposed you could also use your .htaccess rights to create some redirects, and fix this yourself? I might need to enable something server side still for that, but in theory, it could allow you to manage your own breakage.
Jan 22 2020
I took a look at the .htaccess file on the site, and visited the English and French pages that would give a 404:
Dec 29 2019
Strange, I was able to resume file downloads just fine on my system. I can't speak for this app/addon/extension that you are using, however. Perhaps something is blocking range requests on your machine?
Sep 7 2019
Create a file called .htaccess in the top directory of the output html files for the language with the contents:
Sep 4 2019
It would appear that we cannot use ErrorDocument Apache directives in a <Location> context. To manually do this, we could have to define a hard-coded path for each language and version combination. Clearly this doesn't work well over time!
Aug 6 2019
Aug 5 2019
Aug 3 2019
Okay, seems that specifically it was:
I'm wondering if it's:
An old Blender 2.77 redirects to https://developer.blender.org/maniphest/task/create/?project=2&type=Bug and shows:
The logs show:
Jul 16 2019
In general, you don't want to trust your certificates online, in case of hack. But I think if you take reasonable precautions with your signing, you should be okay. For example, have a signing VM that is isolated and only able to mount the filesystem of the buildbot to sign the exe (NFS, etc.).
Feb 4 2019
Feb 1 2019
I forgot to mention that the old vhost docroot files have be entirely deleted, as well as the original database. The old docroot is a mere empty skeleton, needed to satisfy the Apache docroot path, as well as provide a means for Certbot (Lets Encrypt) to acquire its certificates. Once the snapshots rotate enough, the space from the old files will be reclaimed.
Good to hear.
Jan 31 2019
Dec 20 2018
Dec 16 2018
Dec 11 2018
Saw your email having problems assigning this task to yourself. @Sergey Sharybin (sergey) can hopefully look into the Phabricator permissions for you.
Dec 10 2018
Dec 6 2018
Dec 2 2018
And you wonder why I never wanted to open up this can of worms ;)
Nov 19 2018
Oct 30 2018
Oct 29 2018
Can you list all files that are in this directory?
This area has been off limits for a long time by the previous administration:
Oct 4 2018
I think that dev/ is actually correct, isn't it? It tracks the master of git, which if anything should have it's git commit revision in the actual sphinx files changed to be the git revision or something perhaps? I can definitely foresee a problem is search engines see multiple copies of 2.xx in the page content.
@Brecht Van Lommel (brecht) Actually, it always linked to the head of git master, which used to say 2.79. It's only because it naturally changed that it now says 2.80. Anyway, there might be some issue here since we do a regex that matches urls to redirect, but only en and fr languages were given to me, which would be a bit of hassle to try rip apart the regex's and config entries that match the languages to deal with the fact that Aaron only uploaded partial. So TL;DR: he only uploaded 2.79 tar balls, so there is nothing to "keep" at 2.79 since it was a rolling target in the first place and we need to do a final one time build on the manual.
Sounds like your mess. Please leave me out of this and future conversation. Thanks
Sounds like the old pages need to be migrated, and possibly some redirects added, exactly like you just said above. IIRC, we've discussed this several times already? I assume you've finished migrating the old wiki? I could have sworn that's why I gave you the import/export access a month or two ago.
Aug 14 2018
Ah, there was also a left over cruft temporary lock file (I use them to prevent multiple runs of builds) that was left around blocking engilsh. It should be up to date now.
Oh, I forgot to rsync the base manual actually! I only did the languages. Check again in about 5 minutes, it's running now.
Seems that on or around the 11th I did some port maintenance and stopped cron so that the manual wouldn't try running while I was working. Unfortunately I also forgot to restart it. As well, there were actually other issues WRT the new IP being used that would have blocked things. I think it should be all working now though.
Aug 1 2018
Poke me when you have the branches all working and building so I can figure out the back end stuff and have something to test on the web server for redirects.
Jul 31 2018
Jul 30 2018
May 9 2018
Some useful settings for the GA folks: https://support.google.com/analytics/answer/7667196
May 3 2018
Feb 7 2018
May 1 2017
@Pedro Rubini (prubini87) Looks like your problems start showing up when your packets hit spain and get some crazy latency. Unfortunately, we don't have control over the routing of our netblock. It is (generously) sponsored bandwidth from XS4ALL, and tends to get a lower priority and bandwidth limits once it leaves Amsterdam. Traffic to the Americas can even be 15MB/sec while EU is 80MB/sec+, for example. There is simply nothing we can do about this types of problems.
Feb 23 2017
@warp zone (warpzone) Hi, it's been a while, but I think it's the thing I included in the screenshot below. Hope this helps?
Jan 27 2017
Jan 26 2017
I think that there is a built-in phabricator wiki. Not to say we should switch to that (@Sergey Sharybin (sergey) would know best here), but it would conflict with the path a bit potentially?
I can see some good points here. I kinda like the idea of having a wiki in docs as well, but is this what we really want? We could move https://en.blender.org/ under https://docs.blender.org/wiki/ (even as a test to see how it works) and have https://docs.blender.org/ redirect to /wiki/ by default, I suppose. Your call.
I think he meant more like a server treating something like foo.blah as some weird extension in Apache using some weird mime type or extension handler. At least that is what I took away from it.
Well, as I said before, up to you guys. The server shouldn't care about a period in the path for a directory though, just an FYI.
@Aaron Carlisle (Blendify) out of curiosity, why the underscore? Is that common practice for versioning, in blender or anywhere else?
I assume that you are the CSS guru of the group, and was hoping that we could take care of tweaks to the CSS for the /api path together? Of course I am here to get the changes live and tested with you! Let me know when you want to get together and knock it out of the park, etc.
Jan 23 2017
I made a quick sitemap and updated the robots file
Not sure I like /python_api/ much, just for url neatness. I think something like /python/api/ or similar looks better than having hyphens and underscores in the URL.
Jan 22 2017
Jan 21 2017
@Francesco Siddi (fsiddi) Oh, I almost forgot, but that index.htm file also has a blender.org Google Analytics id. Not sure if that was intended.
Thanks @John Roper (johnroper100), but that is controlled by Francesco I think. I would probably also suggest using .html as the extension, as opposed to .htm so we don't have to fiddle with the DirectoryIndex configuration.
Cool, thanks! I put it in place. Probably could use similar for /manual/ and /api/ I guess, but /api/ would be tricky just cause of all the links.
@John Roper (johnroper100) so where is the code? I was hoping to at least get it in place :p
Jan 20 2017
So far I have the following things done for this task:
Jan 19 2017
The idea has been floating around for a while (I think possible from Campbell and I discussing it?). Either way, I am obviously for the idea. A bit of the reasons I had last we discussed were security related more than anything. Here are some of the valid points that I could find that we've discussed in the past already, to try bring things into one place for us:
Sep 13 2016
Also seems that the link for the Webby Awards doesn't resolve in DNS either. :(
Thanks for the report, closing.
Sep 7 2016
Edited the js file. Should be fixed now according to IRC.
May 12 2016
No, there are php scripts in the maintenance folder in Mediawiki installs that let you do stuff that may or may not be available through the web UI. The extensions I think are more meant for people without shell access.
There is a problem with the current wiki in that we cannot add new extensions. Normally when you add an extension you need to run an upgrade script to extend the database schema, but this script is broken in the current database due to a problem with Latin/UTF problems, so we wouldn't be able to activate new extensions. The problem gets fixed when we upgrade Mediawiki though, so the new system would be able to run these extensions just fine, and I believe are even included in the new site.
Apr 12 2016
Apr 11 2016
The problems with Naiad is (currently) the Nav tree is missing. The problem with Any of the stock skins is that we have a bunch of Naiad related cruft in the templates that make a stock nav area break, so things need clean up if we want to go that route. It doesn't matter to me either way; I am just letting you know that if we go with a stock setup, there is a lot of work needed to clean things up and bring it back to a stock setup.
Apr 9 2016
I don't know that I would go so far as to remove the old 2.4/2.5 manuals that exist in the wiki as they are the only manual that exists for them, unless people feel we could just assume it to be deprecated and removed from existence.
Mar 20 2016
Ah yes, we changed the wiki to be https a few days ago. I have updated the BlenderTags plugin to use https and wiped the cache. Everything should be working again now.
Nov 24 2015
Nov 24 2014
Doesn't seem as cut off on my Chrome here, but perhaps Francesco or Pablo might be able to take a closer look.
Oct 10 2014
Ok, I just upgraded Blender to c2d6de8e20 and it still happens.