Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Jurien
Features / Re: New revs
« on December 9th, 2017, 08:47 AM »
Quote from Nao on December 8th, 2017, 11:02 AM
[Commit revision 3897716]
  • Last privacy fix was generating database errors for non-admins. (Load.php)
commented on 3897716
Test yours or other website's with Google's website test tool
Some screenshots taken from (Lumia and Samsung Galaxy)
With Forum Theme Wilderless set as Mobile standard.
Features / Re: Language revs
« on April 18th, 2017, 07:40 PM »
Quote from Nao on April 17th, 2017, 05:21 PM
I'm absolutely for any new translations.

All I want is a clean repo with just a single commit for all of your files. That's all... Just create a new repo locally from Github, move your new files to the dutch folder, right-click them all, "Add", then commit, and send a single pull request (you can do that one from the Github website as long as it knows your repo is forked from mine, IIRC). It's really easy... It just takes a couple of minutes. Not the couple of hours it took you to upload everything manually...
Well i am sorry it was not my intention to cause you so much trouble,but i can't upload files directly into language/Dutch because file uploads require push access to your repository.

So i compare base fork with the head fork,and drag the remaining files into my repository.(Github is what concerns to me a struggle but i am trying to understand the logic behind it )

Create a new branch for this commit and start a pull request named remaining dutch language files.
4 commits are still open (just don't now how to deleted the first 3 commits),but the last one ¨Upload remaining files¨ remains all the not yet added dutch language files.
Features / Re: Language revs
« on April 17th, 2017, 02:40 PM »
Quote from Nao on April 17th, 2017, 02:19 PM
@Freñch, please stop committing individual files and sending pull requests for those!
Also, move them to the proper folder!
What do you mean it looks like you don't want the dutch translations (first you don't react on pull request and then you ask for zip files) i create new files again and send them with pull request.

 :edit: Also committing language files plugins topic_solved
Quote from CerealGuy
Better change it in Credits.php.
Thanks that's a lot easier to do,accept for the license that looks horrible with Https
Https on the credit page links is possible,now the links on the credit page redirect you to
Code: [Select]
$txt['credits_wedge'] = '<a href=""target="_blank">Wedge</a> is copyright © %5$s by <a href=""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]
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.
#Who.english.php <->Website credits page
No referral to the secure connection (SSL server certificate) and this also applies to the license and authors reference

$txt['credits_wedge'] = 'Wedge is copyright © %5$s by %1$s, all rights reserved. It is distributed under the Wedge license.';

When for example change the link into:
$txt['credits_wedge'] = '<a href=""target="_blank">Wedge is copyright © %5$s by %1$s,all rights reserved. It is distributed under the Wedge license.';

Referral to the secure connection is then oké.

 :edit: Also includes almost all links in Homepage
The Pub / Re: PHP 5.4?
« on March 18th, 2017, 02:30 PM »
Quote from Nao
Since Wedge is 5.3+, maybe it's safe to simply up the min reqs to 5.4..?
Well PHP 5.3 is by far the slowest PHP version,PHP 5.4 and PHP 5.5 are slightly faster,(all approaching end of life and upgrading is advisable),PHP 5.6 however is the old stable version,so i would say minimum recommended PHP 5.6
The Pub / [XML] Re: Wedge&PHP 7
« on January 22nd, 2017, 03:49 PM »
Had a weird issue with SimpleXML,got a error message when I went to installed plugins,and could not approach plugins anymore.

Be able to solve this issue,by installing php7.0-xml
Code: [Select]
sudo apt-get install php7.0-xml
followed by a restart service apache
Code: [Select]
sudo service apache2 restart
and after that a reload
Code: [Select]
sudo systemctl daemon-reload
Archived fixes / Re: Don't Show Captcha
« on January 2nd, 2017, 06:18 AM »
Anti Spam->Configure Captcha images:
Is the Use of animated captcha images ticked.
The Pub / Re: Wedge&PHP 7
« on January 1st, 2017, 10:06 AM »
Wedge is doing well on my local why not give it an try on my hosted server.
Set PHP 7 as first using PHP version selector (DirectAdmin)

PHP version Wedge is now 7.0.8 instead of 5.5.37

Conclusion so far no issues.In my opinion Wedge is compatible with PHP7.
(click to show/hide)
For other Forum users who being fobbed off with false promises this is another good reason to make the switch to Wedge in 2017
The Pub / Re: Wedge&PHP 7
« on December 31st, 2016, 09:45 AM »
Quote from Nao
Currently using PHP 7 on my localhost to test my new site...
On my local test server (RaspberryPi) also using PHP 7

Made the decision to install PHP 7 alongside PHP 5,so i have the ability to switch back.

Disabled module PHP 5 and enabled module PHP 7 and restart service apache2

So on my local server up to now everything works properly.
@Nao I know you almost on your one as developer,but what are the prospects for PHP 7 and Wedge sources


 1. B.t.w is there a way to donate some money...where's your donation button on the forum :hmm:
Archived fixes / Error Subs-Template.php
« on December 24th, 2016, 11:31 AM »
This error appears when guests or members select and view Post Feed,is there something wrong in line 166.

[Commit revision ff49935]