Peter Knight

I'm getting lots of errors on a Processwire site I moved. It's a new host and it's my first time trying their platform. I'm not sure if this is a hosting issue or a problem caused by the move. If I list them below I'd be interested in your thoughts. Error displayed when completing a contact form Error: Exception: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away (in /home/u752001136/public_html/wire/core/Modules.php line 2981) #0 /home/u752001136/public_html/wire/core/Modules.php(2981): PDOStatement->execute() #1 /home/u752001136/public_html/wire/core/Modules.php(3381): ProcessWire\Modules->getConfig(Object(ProcessWire\ProcessPageSearch)) #2 /home/u752001136/public_html/wire/core/Modules.php(586): ProcessWire\Modules->setModuleConfigData(Object(ProcessWire\ProcessPageSearch)) #3 /home/u752001136/public_html/wire/core/Modules.php(1246): ProcessWire\Modules->initModule(Object(ProcessWire\ProcessPageSearch), false) #4 /home/u752001136/public_html/wire/core/Modules.php(1141): ProcessWire\Modules->getModule('ProcessPageSear...') #5 /home/u752001136/public_html/wire/modules/AdminTheme/AdminThemeReno/default.php(27): ProcessWire\Modules->get('ProcessPageSear...') #6 /home/u752001136/public_html/wire/core/admin.php(176): require('/home/u75200113...') #7 /home/u752001136/public_html/wire/modules/Admin This error message was shown because: site is in debug mode. ($config->debug = true; => /site/config.php). Error has been logged. Error displayed when using the Upgrades module and upgrading from 3.0.62 to 3.0.93 Pressing the Backup Database Now button displays Error displayed randomly in the Admin Notice: Undefined index: local in /home/u752001136/public_html/site/assets/cache/FileCompiler/site/modules/ProcessWireUpgrade/ProcessWireUpgradeCheck.module on line 266 Notice: Undefined index: title in /home/u752001136/public_html/site/assets/cache/FileCompiler/site/modules/ProcessWireUpgrade/ProcessWireUpgrade.module on line 209 Notice: Undefined index: local in /home/u752001136/public_html/site/assets/cache/FileCompiler/site/modules/ProcessWireUpgrade/ProcessWireUpgrade.module on line 211 Key questions is wether this is a setup issue or simply a shared host with too many sites and not enough resources.

Solved it. I had just assumed that allowing SMTP processing by 3rd parties was a basic feature of mosts hosts. Unfortunately my new host (A2 Hosting) actually don't allow this unless you're on a high level plan. :-/

I moved my site over to a new host and am starting to see errors on my contact form which uses FormBuilder and routes via WireMailSMTP When I submit a form, I receieve the following I wondered if this were a WireMailSMTP issues and tried the Test Settings checkbox The thing is, my PostMark App authentication credentials haven't changed in the move. Just to be sure, I have pasted them in place again with the same result. I then tried to create new Server API tokens, hooked these up and had the same error. I don't believe this is an issue with PostMarkApp (just a hunch) and wondering if anyone had any ideas? Wondered if it might be an issue with the new host stopping somewhow outgoing connections to PostMarkApp etc?

I think that's one of the biggest challenges I face and practically impossible to retrospectively remove data. As an example of the digital footprint user data can have, here's a good example of the headache involed. server backs up a copy of a site. gets uploaded to dropbox which stores multiple archived versions of backups my NAS syncs with my Dropbox account and downloads the same backup. NAS does both snapshots and incremental backups NAS also backs up backups to Amazon S3 and/or amazon glacier My own Mac runs CrashPlan or Syncplicity or Time Machine That's not even considering the backups my host is doing internally :-/ If I had a request from a clients customer to remove their data from the database it'd be a real challenge to perform this thoroughly. I'll probably look at stream lining my backup strategy but we loose a certain amount of redundancy in the process. Reading the GDPR guidelines and the part about anonymising user data I'd love to see this a priority with Processwire. Maybe Formbuilder gets some way of collecting data but that data is only visible to logged in users. Having a compromised database would reveal nothing. Maybe when creating a field called FirstNam there's a new setting which would anonymise the entries to anyone without the proper permissions.

Yep same here. Not sure if it's a bug or intentional. I might file it on GitHub

Thanks for the help @kixe and @kongondo I got it working with a small change. It only works when add the name of the template to the selector. <?php $mostRecentPage = $pages->get("created_users_id=$user->id, sort=-created, template=places");?> Luckily in this project, my clients only create pages based on this template.

Thanks @kixe Couple of questions for you Do I need the sort in there? I'm only trying to retrieve values from the single last created page. I've tried the following which outputs nothing <?php $mostRecentlyCreatedPageByUser = $pages->get("created_users_id=$user->id,sort=-created"); ?> <!-- START: Information --> <strong>City:</strong><?=$mostRecentlyCreatedPageByUser->city ?> <br/> <strong>Miles:</strong><?=$mostRecentlyCreatedPageByUser->miles ?>

On the road and typing on mobile. Hope this makes sense... I have a loggedin user (current session) I want to display to that user some values from the their most recently created page (singular) Is this the right direction to be looking? http://cheatsheet.processwire.com/users/users-methods/users-find-selector/ Thanks

Hi @kongondo I have this site running on two other servers with the same version of PW, PHP. So 2 out of 3 work fine. I'll have to do a little forensic investigating.

Am i right in thinking this is a PHP 7 issue and not so much a Processwire issue? General google seems to suggest so. Just moved a site to a new host and getting following on a simple call Fatal error: Uncaught ArgumentCountError: Too few arguments to function ProcessWire\Pageimage::size(), 1 passed in /home/site.not/site/assets/cache/FileCompiler/site/templates/team-detail.php on line 43 and at least 2 expected in /home/site.not/wire/core/Pageimage.php:519 Stack trace: #0 /home/site.not/site/assets/cache/FileCompiler/site/templates/team-detail.php(43): ProcessWire\Pageimage->size(150) #1 /home/site.not/wire/core/TemplateFile.php(287): require('/home/...') #2 /home/site.not/wire/core/Wire.php(380): ProcessWire\TemplateFile->___render() #3 /home/site.not/wire/core/WireHooks.php(714): ProcessWire\Wire->_callMethod('___render', Array) #4 /home/site.not/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\TemplateFile), 'render', Array) #5 /home/site.not/wire/modules/PageRender.module(514): ProcessWire\Wire->__call('render', Array) #6 /home/site.not/wire/core/Wire. in /home/home/site.not/wire/core/Pageimage.php on line 519 <?php foreach($page->images as $image){ $thumb = $image->size(150); echo "<img src='{$thumb->url}' class='team-photo-detail' alt='{$thumb->description}'" ; }?>

Nice site @patricktsg Good to see another Irish user of PW here. BTW love the 404 page

You don’t have something in the config file which includes the /dev/ host?

Very simple. But it's another template. How do you feel about that Vs just hardcoding the logout into the HTML itself.

Agree. Even for small apps I'd rather keep my clients away from the admin. BTW in my own scenario mentioned above I only have 10 staff members of my client using an App. None of them would even know how to view HTML so I'm not too worried about them seeing a logout page. So you place that in a custom logout template? I get it now.

I have been around the forums on this and can't seem to find my answer. I want to create a html link that forces a user logout. I've seen $session->logout() but I'm not sure how to use it with <a href="#">Logout<a/> This seems to work (my own hack) from inspecting the admin logout link. Just not sure it's the official way <a href="/processwire/login/logout">Logout<a/>

Great location and boat though.

Same here on 3.0.88. Initially I thought it was a UIKit theme issue but I notice your 3.0.62 isn't running this.

@bernhard Thanks for the VSCode mention on the roadmap thread. It's certainly more visual than the terminal. I'd also like to highlight Tower for Git for designers looking to approach GIT via a more visual UI.

I completely forgot about the dev/staging/live workflow too. +1 for that That's a great source of inspiration. I particularly like the detail and options within that Addon such as 1. Pre-saved migration profiles 2. Push / Pull and Export options 3. Push / Pull site URL and secret keys etc etc I found a few more such as Craft Migration Manager and MODX Cloud have a very easy site inject service although it doesn't give you many options re. which tables, fields etc to import. Just a small point about GIT. I know many of you guys are very comfortable interacting with the CLI and GitHub. Some of us here wouldn't be as strong in that regard so it'd be great to see integration with GIT but not so great if the Module depended on it etc.

That's an amazing list of 2017's features. Seeing them in a single place makes you appreciate how lucky we and our clients are. Thanks for another incredible year of updates. I imagine everyone's wish list is different. This is what I'd like to see natively in PW. I know some of these are already available as Modules so no offence if you're reading this and have already put tons of work into creating something similar. Processwire Multi-Admin A Processwire dashboard which allows me to monitor multiple installs across different servers. This dashboard would list my installs, version number, and display available upgrades (Module and Core) and allow me to update above from central place. It might show me logged in user(s), uptime etc. Media Manager A built in MM which acts as a single place to manage all uploads. Using the MM you can find, list and edit any uploaded file/image. and its versions. Add tags, crop, delete, rename, copy, bulk upload etc Furthermore the MM should work with user permissions so a MM for me might list different assets than an editor etc Importantly, the look of the MM would be consistent with what's already in place and the new UI Kit theme. SEO A native SEO Module that is maintained and updated as modern SEO evolves. Image Cropping Pre-set image crops and a way to define and manage them. That's it :-/

In the screengrab attached my header is grey and has a height of 40mm. The text reading 12345 and everything after that is not part of my header and is wrapped in a DIV. Is there some trick to getting the content to start below the header and not overlap as such? My actuall CSS is very simple right now with only the header having a height. I could always give the body an absolute position but thought I'd ask first.

What happens if you create your own index.php file. Does that also prompt a download? Will help isolate if this is a server or a htaccess or PW issue.

Hey @szabesz That's interesting. I wonder if it's working for you in that manner because you're using the root dbuser and the IP etc. Who knows ! I too don't *really* need to try run PW on Synology. I have a few "proper" servers so it's more for my own fun and curiosity but that info is helpful. Good to know it works too as I ran into issues with my htaccess file and general permissions. Otherwise I love the Synology NAS. It's probably the best thing I've ever purchased for my office. Backups, streaming, file sharing etc etc. It's all there. Running a PW site from it would be the cherry on the cake.

On the screengrab below, are the dots before the paths typical or a misconfiguration somewhere? I don't recall seeing them on other new installs.

If you're trying to install ProcessWire on a Synology NAS using the WebStation service, please refer to notes below. I've created this mainly for web searches. I'm going to assume that you're at the installation screen and the first issue you'll have is trying to connect to a database. There's 2 things here you need to note MariaDB is running on Port 3307. You're probably used to running on port 3306 and this might even be what the installation screen pre-populates The Host field must be set to localhost:3307 and not just localhost