pwired

All my sites are done with 2.7.x so I am very happy about everything I just read about the 2.8 release. Thanks !

Thanks Horst for adding this to it. I tried it and all code is working. Moving around pictures in the back end seems so easy now. I simply added the code at the beginning of my home page template file, opened the website and reloaded the home page. Which makes me wonder now. Maybe it is an idea to reserve a template file in processwire specially for executing code occasionally like in this case ? Anyway, the more I learn about the api, like in this case, the more it becomes a pleasure to work with processwire.

You guys make it look so easy Thanks for the example code and that link. Code works perfectly

Hi I have a bunch of pictures in a page called project. Now a project is finished and a new project will be started. That means I first have to copy all the pictures to a dedicated page where the finished project will be shown and then delete all the pictures in the page project to make room for new pictures. What would be the best way to copy a bunch of pictures from one page to another ?

https://processwire.com/talk/topic/6417-processwire-profields-table/?p=63119

Laravel is popular in the processwire community. But look also around where you live what software companies there are looking for php coders such as zend or symphony so you better learn a framework that you both can use in processwire and work with in a company nearby.

Thanks for this one and added to the templates. Does this template allow for adding new blog posts and send a contact form ?

It will produce spaghetti and bloated code like they all do.

"site" refers logically to files needed for the website. Isnt the processing done in the "wire" folder ? So I think conventions are already quite alright.

I use wireRenderFile because it lets me organize and edit html/php code (in pocketgrid) for the front in a very easy way. Just an example: in the templates folder I have a subfolder called views where I keep the files that hold the html/php to show the webpages or parts of the webpages on the front, for example the header, topnavigation, subnavigation, picture sliders, body content, footer, etc. etc. I also have a folder like slider where I keep the html/php code for any picture slider used. Here is a simple example where I have the html/php code for the body content on the home page inside the file _home.php. And this is what I have in the homepage template file: $view = "views/_home.php"; $layout = wireRenderFile($view, array("homepage" => $homepage, "sitepage" => $sitepage, "content" => $content)); Another advantage is that I keep my code clean and easy to view inside pocket grid. For example for a used picture slider I keep all the html/php code inside the file _slider1.php that resides inside the subfolder slider in the templates folder. This way I have no picture slider html/php code flooding my pocketgrid setup and my pocketgrid setup stays easy to over view. <div id="pictures" class="w80 block"> <?php include($config->paths->templates . "slider/_slider1.php"); ?> </div> Like I said this way I can keep html/php very well organized. When I need to edit or change something I know exactly where to find and edit the code. I dont think you can keep the same easy way of organizing your html/php in separated files _name.php when using $page->render() or $page->renderValue().

Exact same case here in a thread with some good reads and solution: https://processwire.com/talk/topic/13781-problems-after-installing-remote-copy-to-local/

Could be a caching/memory problem. Try to trace it with a tool like monyog and look for any bottlenecks happening inside the database.

Start task-manager and see if there is a process with unusual resource use. Check how many apache processes are running. Try to use 127.0.0.1 instead of localhost.

Just my thought about how to improve developing local and what others are thinking about this. No need to explain that there are many good reasons to always have a working local copy of the project or website you are working on (in case the site gets hacked, problems with your hoster, moving to another host, etc. etc.) However you have to deal with two problems: 1. in time the website grows in size and it takes longer and longer time to synchronize the website between your laptop and the host, and 2. the online database will always be different from the local database. You cant just synchronize the online database with the local database without the danger to erase something in the online database. So now I changed to develop with 2 windows open: one window where I work local and a second window where I copy the same work online. This saves me 1. the increasing time to synchronize the site folder and 2. it also saves me the problems with synchronizing the online database with the local database. However I have to do my edits both locally and online but it is a working solution. What are you guys working solution in this ?

If I develop a website locally in a wamp server in a subfolder like /www/subfolder/ I know I have to uncomment RewriteBase in the .htaccess file and configure it to RewriteBase /subfolder/ After uploading the locally developed website to a host directly in the root, (besides database credentials, salt and httpHosts) will it be enough to have RewriteBase commented out in the .htaccess file ?

Website has a nice design. How did you do the popping up pictures ?

Thanks for mentioning Alpaca Forms didn't know about that one and looks very usable. Is Alpaca Forms not powerful enough for your call center project ?

Google changed its use for Google Maps. Since 22 of June 2016 you no longer can use (embed) Google Maps without a registered api key bound to a domain name (called a referrer by Google) Just for the record: in Googles developer page where you have to register a Google Maps api key, they show a misleading dot after the first forward slash in their example: */.domain.com/* Only when I removed that dot my Google Map in a webshop showed up again. Anyway, read it all here: https://developers.google.com/maps/pricing-and-plans/standard-plan-2016-update

Site looks very good, wished I was there when you made it

First set it up with plane html, css and js. Use the examples on the owl carousel website. Once you have that part working you can import it into processwire.

Your welcome, glad it worked out

Dont copy your pw installation. You want to be sure that your new destination environment is compatible with processwire. On your new destination, install a fresh new installation of the same processwire version with the same profile as you did with your running installation. If this doesnt (in your case see if login works normally) work you know you have to check your host settings, if this works then go on delete the site folder on your new destination and copy over the site folder from your running installation and make the salt the same in your config.php. Empty the database on your new destination and import your sql file. Check again if at this stage you can login normally. After this you can go on upgrade your processwire version.

A personal thank you for these tutorials making how to structure in processwire easier understandable.

Good find Adrian. Not only an informative but also a very good looking website.

Thats very Impressive !! Now we have already two good references for answering returning question about Processwire scalability/performance.