Recently Browsing 0 members
No registered users viewing this page.
I've been working on Processwire for two months now. Structuring the website as needed. Unsure why but I'm getting this one now. Seems my fields has crashed.
I've tried googling some answers but can't seem to find a step by step guide on how to rectify this. Any advise? Practically new on this.
I have a website in a production environment and I want to duplicate it in a local environment. I exported the content of the website (with the 'Site Profile Exporter' module) but I cannot use it actually. I've got an issue with the database. I imported this one in MAMP then.
I also exported the pages (with the 'ProcessPagesExportImport' module), but I cannot import it to my local website because the fields don't exist. So I created this fields, but I have this error :
How can I use the elements that already exist and are presents in my database? How can I duplicate correctly the templates, fields and pages?
Thanks by advance
PS: Sorry if my english is bad
Hi. I'm working on building my first processwire site, and I want to make sure I'm getting it right. I'd appreciate any feedback.
I have a `vendor.php` template/model that will contain companies.
I need to give users the ability to rate (1-5) that vendor. So I think I need to build a `vendor_rating.php` model/template with fields `rating` (int), `user` (ref), `vendor` (ref), and perhaps a textarea for `review`. Then, in the vendor template I will call and cache the average vendor rating for display. I don't actually want to display the individual ratings anywhere, so I guess I still need to figure out how to do an ajax call from the front end.
Here's the thing. This structure is almost identical to "comments" with only one extra field for the `rating`. So should I just extend that in some way? Or stick to my current path and make a new model/template?
I'm trying to figure out how to sync fields and templates between staging and production environments.
I've found Migrations module by Lostkobrakai, but with use of it all the fields and templates must be created by API, which is kind of uncomfortable.
I also tried ProcessDatabaseBackups module which can export only certain tables, but I don't think it's the best practice to do that.
How do you guys solve this problem? It's very annoying to setup everything three times (dev, staging, production).
Thanks a lot :)
I have been reading about Multisite, but it kinda bugs me that every topic talks about having both admin and database same for multiple sites.
I have a project where customer tests it by adding content to the site, while I still need to do some changes here and there in code, maybe some in database. If something crashes for a while, customer can't keep testing, which is a bit problematic.
Is there any way that I could have two separate versions of one site ("production" and development) that share the same database, but are otherwise independent? Just the thought of having to migrate database every time I want to show client something new gives me anxiety 😁