Recently Browsing 0 members
No registered users viewing this page.
Existing PW site version 2.7.2 core running on php7.1. Site is perhaps 7 yrs old and never misses a beat. Can't speak highly enough about this solid version, but....
As new php versions are released (v8 in the next year I think?) and each seems to get quicker I'm looking at upgrading to php7.3 or 7.4 and upgrading the site to PW v3.x.
I've been away from the forums since v3 was released so don't know much about it. I guess it's stable as it's been around for ages now, but what I'm wondering is:
what are the real advantages of upgrading to v3 for a site which is actively used but with only periodic development. And what are the disadvantages if any? Is there any speed impact (good or bad) in either general site speed under 3.x or admin-use speed/ease of use? any issues with either PW version with newer php versions (>7.1) I should know about? is there any good write-ups/vids about new features etc of v3 compared to v2.7? Thank you
I had upgraded my Apache configuration to include PHP7.2 and PHP7.3 for a Laravel-based script on the same server. Somehow it/I messed up a previously fine Processwire site, in a very confusing way.
The site still looks fine, but editing template files has no effect whatsoever. It is stuck on some kind of cached version. I have already disabled PHP7's OPcache, cleared browser caches, etc, with no effect.
The pages now apparently come from PW's assets/cache/FileCompiler folder, even though I never enabled template caching for this site.
I have tried adding "namespace ProcessWire;" to the top of the homepage template file, but then I get this fatal error:
My functions.php file pulls data in from another Processwire installation on the same VPS with the following line:
$othersitedata = new ProcessWire('/home/myaccount/public_html/myothersite/site/', 'https://myothersite.com/'); That apparently still works fine; the site still displays data from the other installation, but via the "cached" template that I am now unable to change.
I don't know where to start with this mess. Does any of this sound familiar to anyone? Any pointers in the right direction would be much appreciated.
Adding "$config->templateCompile = false;" to config.php results in the same fatal error as above.
Interesting Conference / Talk from Rasmus Lerdorf, creator of PHP.
A colleague of mine is trying to get our site running on his local Ubuntu LAMP Setup (Ubuntu 17.10, Apache 2.4.27, PW 3.0.62, PHP 7.1.11)
When he types in the Homepage URL, he's getting code outputted instead of being executed.
Does any one know why?
Just Figured it out.
Apparently, it's a new PHP7 security feature that disables from code executing if the code module starts with <? instead of <php
I'm using MAMP locally so I'm guessing MAMP is somehow circumventing this but LAMP isn't.
I'm posting this so people can save themselves hours pulling their hair out.
I'm in the middle of setting up a new PW site and cloned in master from github, but was a bit surprised to see that ProcessWire isnt yet PHP7 compatible.
I mean, it works. But at the top of every page you get a depreciated notice:
Is there any timeframe for when PW will be updated to PHP7? This looks like a fairly minor thing to fix, it's just a bit surprising it's not already done.
There's a very strong push to get people updated to PHP7 in the development community, and all the major hosts seem to be pushing it too, likely due to its lower resource usage, and speed improvements.
If this is something not yet planned, I take it I'd be ok to submit a pull request on github with some, if not all the updates needed to get this compatible with PHP7?