Recently Browsing 0 members
No registered users viewing this page.
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 😁
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.
After temporarily using Module Image Extra, which I completely removed, I had some troubles with my imagefield (unused table columns).
So I just imported a previous version of this column via PHPmyAdmin, which worked pretty well.
Anyways, in Processwire Backend all image tags are gone, although they are OK in the database.
Other image related things work (thumbnail, title etc are OK).
Is there any way to recreate all the images or something? Or may this be an cache-related issue?
Thanks in advance 😃
We have many booking calendars made with ProcessWire (own databases) and I want to do a web app (SQL) which allows user to log in. First, the user chooses the right calendar and then (s)he have to log in. The user can be from any of those calendars and the app is not running on ProcessWire (it can if necessary). So if there any way to make sure that the user has rights to the calendar (s)he tries to log in and if the password is correct.
Is there any better way to do this? I could also use PIN codes or something, but those need to be encrypted too.
Multiple ProcessWires A lot of users per ProcessWire Everyone can log in to the web app (when using right calendar)