User tests: Successful: Unsuccessful:
Pull Request for Issue #21969 .
Changed language variable PLG_QUICKICON_PHPVERSIONCHECK_SECURITY_ONLY.
Removed the recommendation for PHP 7.x, called it more generic "newer version".
Short sentences with the necessary information.
Replace the ini file and check the warning in Joomla control panel if you have PHP 7.0.x.
Quickitem phpversioncheck needs to be activated.
Clear warning message.
none
Status | New | ⇒ | Pending |
Category | ⇒ | Administration Language & Strings |
Title |
|
I am fine with any changes as long as it is formally right. Please go ahead.
My version is shorter, has three short sentences with the most important information. I like to keep it short and precise.
The grammar in the current text is not really up to the mark, so I took the chance to change that. The translators have to touch the text anyway and I don't see too much work for them added. Looking at the German translation the Grammar is already correct.
If we correct it one way or the other isn't really a big deal. If the user understands it it's fine. We should just do it.
I have tested this item
I like the new version. Short and simple.
Unfortunately translators sometimes do not translate but replace english words by words of their own language, which results in difficult sentences. In german I will suggest to use even a shorter Information:
"Your PHP version, %1$s, will reach end of support on %2$s. We recommend upgrading to a newer PHP version soon to keep your Joomla installation secure. Please contact your host for upgrade instructions."
Sounds even better to me, chmst.
The variable for "unsupported PHP version" could use a trim too. But I wanted to keep the hurdles for closing this issue as tiny as possible.
Can we agree on chmst's suggestion?
@StefanSTS commit your prefered version and we will see what happens.
Labels |
Added:
?
?
|
I have tested this item
Thank you. I am no native speaker but looks good for me.
I have tested this item
Tested successfully.
I have tested this item
Tested successfully.
Status | Pending | ⇒ | Ready to Commit |
Ready to Commit after two successful tests.
i still dont like this change as it has changed the meaning of the message and i stick by my earlier comment
@brianteeman In my opinion everything is still in the message except for "faster php".
The former message states three times that the security will be a problem.
"is only receiving security fixes"
"your PHP version will soon no longer be supported"
" before it reaches end of support on %2$s"
This is all covered in:
Your PHP version, %1$s, will reach end of support on %2$s. .... to keep your Joomla installation secure."
I don't see any reason to make the user read so much text which will make some users stop in the middle and disregard the message. What happens to long messages often.
The "faster and more secure" part is a bit of marketing text, not much different than what https://github.com/WordPress/servehappy is proposing for that platform. It's also explaining a benefit to the user to complete the action, not just "oh the software powering your site is no longer supported".
Personally I'd only remove the "PHP 7.x is recommended" bit, in hindsight it wasn't the best of ideas to specify a version in the string (we should've made it a sprintf and dynamically pushed it in).
One thing we need to be careful of, no matter how many times it is suggested these nag messages be revised or removed outright, is making the message too concise. We aren't linking to any external resources explaining the alert or how to address it, so we need to ensure that the message is crystal clear with the text we give users. There is a part of me that feels like this change might be making the message too concise.
The proposed message does not say anywhere that the version of php is only receiving security fixes AND very importantly it makes no mention of the fact that this is a php project issue and not a joomla one.
I am 100% in favour of shorter messages but we can't go so short as to remove the important meaning of the message.
How does that sound?
The PHP project is supporting your PHP version, %1$s, only until %2$s with security fixes. We recommend upgrading to a newer PHP version soon to keep your Joomla installation secure. Please contact your host for upgrade instructions.
Giving warning and error messages a number or some alphanumeric value might be a good idea. Could be easier to find them on a search engine in other languages and someone might even consider to make a list of them with possible solutions. Might be worth to open an issue for that.
Sorry but it still doesnt work for me. It doesnt stress that it is only getting security fixes and not any bug fixes. We did spend a lot if time writing the original string :) We just made a mistake including the version number
To make it a generic message, you have to remove the "faster" too. One of the next versions might not be faster, it might have more features and gets slower. Except you want to keep that advertising aspect. So give us your best shot @brianteeman and we can finalise this before we spend more time changing the text than you spend on creating it. ;-)
I already did #21987 (comment)
Keep the faster? That might be false advertising in future versions. That cannot come from my pull request.
I accept the arguments, so let us come back to the original content (without version number).
Maybe a simple linebreak after every sentence could do the trick and make reading and understanding easier, this was the intention for this PR.
So another try:
Your PHP version, %1$s, is only receiving security fixes from the PHP project at this time. This means your PHP version will soon no longer be supported. We recommend planning to upgrade to a newer PHP version before it reaches end of support on %2$s. Joomla will be faster and more secure if you upgrade to a newer PHP version. Please contact your host for upgrade instructions.
Of course with my strongest protest about the faster. But lets end it.
Is that fine like this?
Labels |
Added:
?
|
The file is changed to the mentioned version above, please test if that is fine now.
Thanks.
If there are any more steps I have to do to finalize this request, please advise. I see all green markers so I hope with @brianteeman 's go, this can be merged.
I have tested this item
I have tested this item
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-09-18 01:26:06 |
Closed_By | ⇒ | mbabker |
The only thing I would change with the original string would have been to remove this part
(PHP 7.x is recommended)
I don't see the purpose of the other changes - which are a complete rewrite adding work for the translators