Recent Posts
11
Https on the credit page links is possible,now the links on the credit page redirect you to http://wedge.org/
Code: [Select]
$txt['credits_wedge'] = '<a href="https://wedge.org/"target="_blank">Wedge</a> is copyright © %5$s by <a href="https://wedge.org/profile/Nao"target="_blank">%1$s</a>
instead of
Code: [Select]
$txt['credits_wedge'] = '<a href="%2$s">Wedge</a> is copyright © %5$s by <a href="%3$s">%1$s</a>

Or perhaps insert the following code in the .htaccess file
Code: [Select]
##-------Force HTTPS connection from a folder-------##
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]
##
12
Development blog / Re: The obligatory Christmas update.
« on March 19th, 04:03 PM by CerealGuy »
Quote from Nao on March 19th, 12:40 PM
I just realized this was my last post on the blog... :^^;:
Oh, and that comment system looks so cool.

I'm guessing I need to make a strong statement about Wedge still being alive.
Thanks to CerealGuy for never giving up and pestering me into coming back :)
Also thanks to Lestrades.com for giving me a good reason to get back to work!
Wedge was the first bigger codebase I worked with and later contributed to. In that
time (and it still goes on) I learned a lot. Not only the benefits of open source and how
much fun it can be to work on project, but also It's the first time that code i wrote and ideas
I have, really get used in projects which aren't my own :lol:.
Thanks for making this possible.
 I hope we can obtain this friendly working condition in the future.
I wish you best luck and success with your LT project  :cool:
13
How about using that <PROT> magic thing we added once for Aeva Media? So everyone using a https connection will get https://wedge.org, everyone else plain http.

But still I don't see any real benefit on using https over plain http on the credit page. What maybe would make sense is that you get forced to use ssl as soon as you try to login. And always get redirected to the ssl url if you are logged in and don't use ssl. Plugin stuff?
14
Bug reports / Re: Couple things to look into...
« on March 19th, 03:25 PM by CerealGuy »
Quote from Nao on March 19th, 11:41 AM
Actually that's because the cli tag didn't have a plugin ID and you're only loading those.
This might be a problem if someone built a mod (rather than a plugin) that still added stuff to the database, but it's unlikely of course.

(This still isn't working yet, ahah.)

 :edit: Was due to the fact that the list tag didn't have 'cli' in its allowed children.
This where part will get removed as soon as the default bbcodes got removed from the database. So only a temporary thing.
15
Quote from Freñiçh on March 19th, 12:37 PM
Quote from Nao
Any reason you'd want to have an exclusive https connection?
Well a secure connection between internet browsers and websites is not a luxury it's a must, allowing to transmit details,passwords or any personal information.
But what personal information would you want to transmit over https here that isn't already encrypted..?
It should be enough that Wedge now fully supports https. ;) (It wasn't the case before.)
The only problem is with avatars, which sometimes use http links so you have to be smart about them.
Quote
So when an users on my Website which is secured with a SSL Certificate chooses to click on a link (on our credit page) it seems logical to me that this must be a secure connection.
Not really, no..?
16
Development blog / Re: The obligatory Christmas update.
« on March 19th, 12:40 PM by Nao »
I just realized this was my last post on the blog... :^^;:
Oh, and that comment system looks so cool.

I'm guessing I need to make a strong statement about Wedge still being alive.
Thanks to CerealGuy for never giving up and pestering me into coming back :)
Also thanks to Lestrades.com for giving me a good reason to get back to work!
17
Quote from Nao
Any reason you'd want to have an exclusive https connection?
Well a secure connection between internet browsers and websites is not a luxury it's a must, allowing to transmit details,passwords or any personal information.

So when an users on my Website which is secured with a SSL Certificate chooses to click on a link (on our credit page) it seems logical to me that this must be a secure connection.
18
Well, IIRC I only added https support to wedge.org for testing. I'm only making use of it on lestrades.com, where sensitive (or more precisely, 'valuable') data can be shared. I keep asking my host to enable http/2 on nginx[1] but she won't budge. I had my websites hosted by someone else so I wouldn't have to deal with keeping a list of installed modules to update, but apparently I'm not the only one not willing to do that ahah.

Any reason you'd want to have an exclusive https connection? Because AFAIK it's a bit slower (5% at least?), and there is no sensitive data here-- everything is open source and passwords are encrypted before they're transmitted anyway.
 1. This would give me a good reason to move everything to https, by making everything load noticeably faster.
19
Features / Re: New revs
« on March 19th, 11:48 AM by Nao »
[Commit revision 0d9d3e4]
Author: Nao
Date: Sun, 19 Mar 2017 11:47:30 +0100
Stats: 1 file changed; +9 (insertions), -29 (deletions)

  • Spacinazi. (Subs-BBC.php)
  • Removed duplicate array declarations, and simplified one of them. (Subs-BBC.php)
20
Bug reports / Re: Couple things to look into...
« on March 19th, 11:41 AM by Nao »
Quote from Nao on March 19th, 12:29 AM
Also, looks like your subs-bbc commit is broken... At the very least, 'list' or 'cli' tags aren't working properly (see New Revs topic). Dunno if it's a problem during the rewrite for 'list', or a problem with external custom bbcode not loading at all.
Actually that's because the cli tag didn't have a plugin ID and you're only loading those.
This might be a problem if someone built a mod (rather than a plugin) that still added stuff to the database, but it's unlikely of course.

(This still isn't working yet, ahah.)

:edit: Was due to the fact that the list tag didn't have 'cli' in its allowed children.