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.
1
Bug reports / [Behaviour] Re: Keep post data on Login
« on August 11th, 2016, 11:02 PM »
If you plan on putting $_POST/$_GET data in hidden inputs, remember that if done slightly wrong is a potential security risk, very similar to the one fixed two or three years ago for the admin login function.
2
The Pub / Re: Wedge&PHP 7
« on July 22nd, 2016, 07:51 PM »
One of the common issues I've seen for php7 and "ours" codebases are: sessions.
PHP7 changed some of the expected returns for the custom session handlers, so session handling may break.
Then, if you use dynamic function/method calls, the precedence changed so it *may* be broken (TBH I don't remember if it was 7.0 or 7.1). list has changed (no more empty arguments).
And I think eval throwing an exception is relevant as well (if you silence the error, that is) and there are some odd changes to foreach as well I still have to evaluate.
This are three PRs related to PHP 7 done to Elk:
https://github.com/elkarte/Elkarte/pull/2339
https://github.com/elkarte/Elkarte/pull/2353
https://github.com/elkarte/Elkarte/pull/2600
PHP7 changed some of the expected returns for the custom session handlers, so session handling may break.
Then, if you use dynamic function/method calls, the precedence changed so it *may* be broken (TBH I don't remember if it was 7.0 or 7.1). list has changed (no more empty arguments).
And I think eval throwing an exception is relevant as well (if you silence the error, that is) and there are some odd changes to foreach as well I still have to evaluate.
This are three PRs related to PHP 7 done to Elk:
https://github.com/elkarte/Elkarte/pull/2339
https://github.com/elkarte/Elkarte/pull/2353
https://github.com/elkarte/Elkarte/pull/2600
3
Support / Re: why i get Error 500 and have alot proplems
« on June 30th, 2016, 11:25 PM »4
Support / Re: why i get Error 500 and have alot proplems
« on June 16th, 2016, 09:43 AM »1- what it database prefix how it write
2- there is a forum work on wedge and it have same proplems but a another forum is perfect and no error happend why?
i got this ErrorCode: [Select] Warning: mysqli_connect(): (28000/1045): Access denied for user 'Zeyad_Ahmed'@'10.2.1.20' (using password: YES) in /home/u289793038/public_html/gz/app/Class-DB.php on line 55
Access denied for user 'Zeyad_Ahmed'@'10.2.1.20' (using password: YES)
5
Support / Re: why i get Error 500 and have alot proplems
« on June 15th, 2016, 10:51 PM »
98% of the times, 500 errors are problems with file permissions/ownership.
Are you using a linux server? I'm not a Wedge expert, but I guess you should make sure the files are 644 and directories are 755.
Are you using a linux server? I'm not a Wedge expert, but I guess you should make sure the files are 644 and directories are 755.
6
Support / Re: I want a wedge support 5.2 PHP IS it Possible
« on June 12th, 2016, 10:15 PM »
I feel it would be kinda tough: Wedge makes extensive use of closures that are supported on in php 5.3+.
Additionally, even php 5.3 is already several years old, there is little excuses not to use at least 5.3.
Additionally, even php 5.3 is already several years old, there is little excuses not to use at least 5.3.
7
Features / Re: About Sphinx search engine
« on January 4th, 2016, 11:48 PM »* emanuele smells spam http://wedge.org/profile/janetfdoss/?area=showposts :P
8
Off-topic / Re: Merry Christmas and Happy New Year
« on December 26th, 2015, 12:12 AM »
A bit late, but Merry Christmas from me too! :D
9
Support / Re: How best to involve the Cookie Bar
« on September 13th, 2015, 10:34 PM »
It's a directive, that each Member State has implemented its own way.
For example in Italy... there is chaos. LOL
Almost any site has put up a huge banner with the cookies warning, and is not entirely clear when and how the warning is really needed and what it shall do. (Actually, I think a good 75% of the sites have implemented it the wrong way, but considering nobody will ever go to the judge for a cookie nobody will ever know so who cares. :P)
For example in Italy... there is chaos. LOL
Almost any site has put up a huge banner with the cookies warning, and is not entirely clear when and how the warning is really needed and what it shall do. (Actually, I think a good 75% of the sites have implemented it the wrong way, but considering nobody will ever go to the judge for a cookie nobody will ever know so who cares. :P)
10
Off-topic / Re: Introduction
« on May 21st, 2015, 11:40 PM »
I felt like that as well.
janetfdoss at least looks very like a spammer:
https://www.google.com/search?q=%22Have%20a%20strong%20interest%20in%20promoting%22%20Prescott
janetfdoss at least looks very like a spammer:
https://www.google.com/search?q=%22Have%20a%20strong%20interest%20in%20promoting%22%20Prescott
11
Off-topic / Re: Windows
« on April 5th, 2015, 03:03 PM »
Ohhh... darn restore points.
In the past it was the first thing to disable in my book. Then I started to forget about them. But for sure, when you need one it's not there. xD
In the past it was the first thing to disable in my book. Then I started to forget about them. But for sure, when you need one it's not there. xD
12
Bug reports / Comment toggle initialized wrong
« on March 5th, 2015, 09:49 PM »
Go to an item of the gallery:
http://wedge.org/do/media/?sa=item;in=269;sort=0
click on "Comment" (at the bottom), nothing happens.
Click again it opens the textarea.
Apparently the textarea should be visible from the start (also because the image shows the "-" and not the "+"), but is not, so the first time the already hidden textarea is closed (again) and on the second click it's finally opened.
http://wedge.org/do/media/?sa=item;in=269;sort=0
click on "Comment" (at the bottom), nothing happens.
Click again it opens the textarea.
Apparently the textarea should be visible from the start (also because the image shows the "-" and not the "+"), but is not, so the first time the already hidden textarea is closed (again) and on the second click it's finally opened.
13
Archived fixes / Data too long for column 'featured' at row 1
« on March 5th, 2015, 09:44 PM »
Clean install of the current HEAD of the master branch.
MySQL 5.6.17.
Creating an album I got this message:
Code: [Select]
The workaround I used is to change the column to tinyint. :P
MySQL 5.6.17.
Creating an album I got this message:
Data too long for column 'featured' at row 1
File: /home/emanuele/webserver/htdocs/wedge/gz/app/media_Aeva-Gallery2.php
Line: 1675
The workaround I used is to change the column to tinyint. :P
14
Archived fixes / Re: install.php, no more. :P
« on January 23rd, 2015, 02:51 PM »
Ohh... not verified enough, sorry... :-[
15