Recently Browsing 0 members
No registered users viewing this page.
Here are the step by step to install and setup ProcessWire with the help of a server management tool - https://cloudstick.io/
1. Create your Vultr compute.
2. Select the Operating system Ubuntu 16.04/18.04/20.04 LTS >> Enter your server root password then click on Deploy now!
3. Create an account in CloudStick and connect your server:
Click on connect server >> Enter your server login details >> Add this server.
4. Your server setup will be done in couple of minutes - The setup will finish less than 8 minutes. Then select your server:
5. Create an account to host/upload ProcessWire: Click on Accounts >> Create an account >> Create Custom Web application:
6. Enter the web application details, such as the email address which you would like to receive the SFTP login details >> web application name >> Domain name >> username then >> select the web application stack >> nginx + apache >> then create web application.
7. Now select the web application then install SSL:
8. Open your email account, and find the login details to connect the server over SFTP >> then upload the source code of ProcessWire:
9. Let us open the domain in browser once the upload finish.
10. Select the profile and click next:
11. Click next to proceed further: Now, you will see an incompatibility issue with PDO-Mysql which can be install in 2 clicks.
12. Go back to the summary page >> Click on easy PHP >> Select the PHP version of your web account:
13. Then it is time to enable PDO_Mysql, scroll down and enable it:
14. Go back to to the ProcessWire installation URL and click on check again >> You can see no incompatibility issue after enabling PDO_Mysql:
15. Click on Next and now it is time to enter the database credentials:
16. let us create the database, db user and grant privilege's to the db user - it is just matter of few clicks and very easy!
Click on the menu Accounts >> Select your web account of ProcessWire >> Click on App Database then create the a database:
17: Click on create database and enter the database name:
18. Create the database user:
19: Go back to the database page and click on Grant user then grant permission:
20. Go back to the ProcessWire installation URL and enter the database credentials you have created in CloudStick dashboard.
Now, it is time to setup your admin user credentials and setup admin area URL:
21. Then you are done:
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
while developing a sideproject which is completly build with ProcessModules i suddenly had the urge to measure the performance of some modules 😉 as a result, say welcome to the FlowtiAppPerformance module.
It comes bundled with a small helper module called FlowtiModuleProfiler. In the first release, even though you could select other modules, it will track the execution of selected Site/ProcessModules.
This will give you the ability to gain insights how your Application behaves.
The Main Module itself will come with 2 Logging Options, Database or PW Logs. Select Database for Charts and Logs...well If you just want your profiles as a simple log file in PW.
You also could choose to dump the request profile into TracyDebugger as shown here:
Dont wonder about my avg_sysload, somehow my laptop cant handle multiple VMs that good 😄
again, dont look at the sysload 😄
I will update the Module in the future to give some filter options and aggregation, but for now it satisfies my needs.
I hope it is helpfull for some.
Module is submited to the directory and hosted at github
Any suggestions, wishes etc. are much appreciated.
what I'm doing is this:
<picture> <source srcset="<?php echo $page->section_three->main_img->first()->size(396,710)->webp->url; ?>" type="image/webp"> <img class="p_absoulte pp_block" src="<?php echo $page->section_three->main_img->first()->size(396,710)->url; ?>" alt=""> </picture> and for some reason it sometimes becomes this:
<picture> <source srcset="/site/assets/files/1057/sektion3_bild-1.396x710.png" type="image/webp"> <img class="p_absoulte pp_block" src="/site/assets/files/1057/sektion3_bild-1.396x710.png" alt=""> </picture> It seems to be related to ->size(). When I don't use ->size() the webp Url is correct.
I'm using the image-field inside a Fieldset(Page). Could that be a problem too?
I just increased the output size by 2px and voila the webp url comes up.
I deleted all variations (webp variation is present in correct size) changed it back to the original size and again: a png url.
I also tried to rename the image and load it up agian.
Thanks in advance guys