Joomla 3.48 error with php 7

[ste...@gmail.com]

Was messing around with php7 and I get this error.

Fatal error: Cannot use Joomla\String\String as String because 'String' is a special class name in /cha/public_html/libraries/vendor/joomla/registry/src/Format/Json.php on line 12

[Dmitry Rekun]

Hi!

3.5.0 will be compatible with PHP7. Wanna test 3.4 on PHP7? Read this http://community.1and1.com/joomla-3-4-php-7/

Dmitry

[ste...@gmail.com]

Thanks Dmitry

I saw the pull request after I posted it. Thank you for the link a 50% speed increase with php7 is amazing.

Steve

[ssnobben]

Hi Dimitri,

I think this is really great and will be a good improvement for Joomla speed and also about the innode problems? will this help innodes problems together with better lower memory usage? I dont think so ?

I only have one site hosted at Siteground shared premium plan "GoGeek Crafted for Real Web Geeks" hosting with Unlimited Traffic, Emails, DBs and 30 GB storage. What they dont tell is about the importance of "Inodes" that limit your progress of your site when its grows.So this is a big problem and of course a selling argument for Siteground for you to upgrade. So all this talk from hosting providers of Unlimited Traffic, Emails, DBs and 30 GB storage doesnt matter if they set this innodes as a measure for forcing you to upgrade as your site grows...

This is the message I got and I wonder if the new Joomla 3.5 and php 7 will have any effect of inodes reduction too?

"We would like to warn you that your hosting account has reached 80% of the allowed inode quota. Once it hits the limit, you will not be able to upload new files on it, or receive new emails and overall, your website might start returning errors when accessed. To avoid hitting the inode quota, we suggest you delete all unnecessary and obsolete files/folders from your account.

To decrease the number of inodes, you need to reduce the number of files and folders on your account via cPanel > File Manager or your preferred FTP client. You may also post a ticket with a list of the files/folders you would like to have removed from your account and our support team will remove them for you for free.

Check out what is an inode and why limit it:
http://kb.siteground.com/what_is_an_inode/

Learn how to reduce the number of inodes:
http://kb.siteground.com/article/How_to_reduce_the_number_of_inodes_my_account_uses.html

In case deleting some files/folders is not a suitable option for you, you may consider upgrading your account to a higher plan. You can order the upgrade it from the Order section of your SiteGround Customer Area.

https://ua.siteground.com/order.htm"

[ssnobben]

Thanks Michael Babker for your hard work on this one..

Cheers!

On Tuesday, 5 January 2016 13:33:18 UTC+1, Dmitry Rekun wrote:

[Hannes Papenberg]

Joomla 3.5 will not reduce the numer of inodes used. Since that number
is more or less directly proportional to the number of files of your
site, this would mean that we would have to remove (significant numbers
of) our code files. Joomla will not reduce the number of files that it
uses anytime soon. The opposite is much more likely.

This is the first time that I heard a hoster to limit the inodes used on
an account...

Hannes

> you may consider upgrading your account to a higher plan. *You can

> order the upgrade it from the Order section of your SiteGround
> Customer Area.
>

> https://ua.siteground.com/order.htm" <https://ua.siteground.com/order.htm>
> *

> On Tuesday, 5 January 2016 13:33:18 UTC+1, Dmitry Rekun wrote:
>
> Hi!
>
> 3.5.0 will be compatible with PHP7. Wanna test 3.4 on PHP7? Read
> this http://community.1and1.com/joomla-3-4-php-7/
> <http://community.1and1.com/joomla-3-4-php-7/>
>
> Dmitry
>
> On Tuesday, January 5, 2016 at 2:15:09 PM UTC+2, ste...@gmail.com
> wrote:
>
> Was messing around with php7 and I get this error.
>
> |
> Fatalerror:CannotuseJoomla\String\StringasStringbecause
> 'String'isa special classname
> in/cha/public_html/libraries/vendor/joomla/registry/src/Format/Json.php
> on line 12
> |

> *
> *
>
> --
> You received this message because you are subscribed to the Google
> Groups "Joomla! CMS Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to joomla-dev-cm...@googlegroups.com
> <mailto:joomla-dev-cm...@googlegroups.com>.
> To post to this group, send email to joomla-...@googlegroups.com
> <mailto:joomla-...@googlegroups.com>.
> Visit this group at https://groups.google.com/group/joomla-dev-cms.
> For more options, visit https://groups.google.com/d/optout.

[brian teeman]

On Wednesday, 6 January 2016 11:20:04 UTC, Hannes Papenberg wrote:

This is the first time that I heard a hoster to limit the inodes used on
an account...

There are several hosts that do this. However I should point out that on my siteground gogeek account with approx 18 Joomla 3.4.8 web sites of various sizes I am only using  118163/450000 inodes which is about 25% of the maximum available

 

[Beat]

inodes limit is a filesystem sanity safeguard. Usually, it's log files or cache files that don't get cleared. Check your /var/log directory, /var/asl and other directories, in particular joomla log if you have logging enabled, joomla cache directory if you have some caching apps. Those are the ones that may get many files and hit the inodes limit.

Beat
/http://www.joomlapolis.com/

[Walt Sorensen]

I've toyed a bit with 3.4.x and php 7. Even though you can get core Joomla 3.4.x to run in PHP7; good luck with running most 3rd party extensions in a PHP7 environment.

It's lots of testing and tweaks to have unstable untested code running under php7 right now. I'm not saying you shouldn't test and report the issues, Just don't expect to have a stable running site right now.

Outside of testing, I'm waiting for official releases of Joomla 3.5 and official 3rd party releases that explicitly state they support PHP7 for my production sites.

[ssnobben]

Thanks Beat.

Cleared out a lot of fles and got the inodes to shink dramatically..total unecessary files in SiteGround filesystem there that I hope helped to get this inodes problem disappear.Now looking good.

[ssnobben]

well this is the reason that I hope we can get J 3.5 out asap so we can speed up the Joomla php7 and the 3pds support for php7 as well.

[Michael Babker]

If third party code isn't already supporting PHP 7 frankly I'd call it borderline garbage.  In the context of Joomla, there are very few if any changes needed for well written PHP code to have worked the day PHP 7 released.  The changes that Joomla core itself needed are backward compatible to PHP 5.3 and mainly related to the uniform variable syntax RFC and new reserved keywords because of scalar type hinting.  Any developer following GitHub would know the effort to start supporting PHP 7 began about a year ago and long before the first alpha release, following those pull requests should have given a clue what changes they'd need to make.

--

You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
To post to this group, send email to joomla-...@googlegroups.com.

Visit this group at https://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.

--
- Michael

Please pardon any errors, this message was sent from my iPhone.

[Walt Sorensen]

Sadly I've found many (even well known) 3rd party developers wait until about 3-6 months after Joomla has an official release supporting something before they even try to add that support to their extensions.

Even with that, I have still found when a support request is filed with a quality developer they usually will make the minor changes needed to support something. 

The biggest issue I have found recently is with some Template/extension developers who claimed "PHP7 is a massive leap" and "J3.5 is only in beta at this stage so even that can't use PHP7 yet" Which saddened me since it was such erroneous statements, and totally misguided coming from a well know and decent group. (although I will say it was mostly opinions coming from one of the support staff) Eventually they did add a review for the patches I submitted that fixed some of the initial php7 issues I found in their code.

Common things I've seen, in 3rd party extensions that needed to be fixed for PHP7 with backwards compatibility for PHP5 .
JString has been depreciated use Joomla\String\StringHelper;
Array to string conversions
Methods with the same name as their class will not be constructors
Uniform Variable Syntax change

from

if (isset($node->$nodes[$i]))

to

if (isset($node->{$nodes[$i]}))

[Michael Babker]

You do realize how much space that is, right?  8 or 9 of the joomla.org properties combined fit under that limit.  Truthfully, a site with that much filesystem data probably shouldn't be on any shared hosting platform, maybe that's what they're saying.

On Sunday, January 24, 2016, ssnobben <ssno...@hotmail.com> wrote:

And SiteGround also now set a file upload limit for 27.63 GB so if you ever have a site that is larger than that and want Akeeba etc to upload and do a Kickstarter forget about it.

I think SiteGround is not a good partner for Joomal anymore...

--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
To post to this group, send email to joomla-...@googlegroups.com.
Visit this group at https://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.

[ssnobben]

Hi that was a typo and misinformation I got from the developer :) sorry we have sorted this out..

To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cms+unsubscribe@googlegroups.com.
To post to this group, send email to joomla-dev-cms@googlegroups.com.

Visit this group at https://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.