IMPORTANT, please fill the questions
We assume you are using Bitnami to deploy your application.
Which version of the application are you using?:
Colleague 1 has wordpress 4.7.4 on wampstack 5.6.30-1
Colleague 2 has wordpress 4.7.4 on wampstack 5.6.30-2
Please choose how you got the application: Installer (Windows, Linux, macOS), cloud image (AWS, GCE, Azure, ...) or VM (VMDK, VBOX):
Wamp was installed with a windows installer, wordpress was deployed by cloning the demo app and linking it to apache following the guide (as a custom app).
Have you installed any plugin or modified any configuration file?:
Installed wordpress (not bitnami module) on top of it. See above.
Describe here your question/suggestion/issue (expected and actual results):
Colleague 1 (me) gave his Wordpress installation to to Colleague 2 to work on, by copying over the app folder under /apps and by creating a MySQL dump file. Since the Windows paths of bitnami WAMP stack were different due to the version, I changed all absolute path references in Apache, Apps, Wordpress and DB dump. So far so good, Colleague 2 resumed the work and everything worked fine for a while.
After adding some content to a Wordpress page with visual composer and saving the page, the site started responding http 304 on every request. Every single file/page request would result in a 304.
I then asked Colleague 2 to hand over the installation, so I reversed the process above and put everything on my machine. With much surprise, everything is working fine.
So I can only think of a missing edit in configuration when I handed over Wordpress to Colleague 2 the first time, but apart from that absolute path, I had intentionally configured everything else with identical names. So I can't think of what might be the problem and I wonder if you could help me out.
Checking the apache log on Colleague2's PC it seems like it restarts everytime I access the site but I'm not entirely sure, as I'm not very sharp on the subject.
Thanks in advance for your support. Have a nice day!
(PS: I know the setup sounds horrible, but since we are in an early stage in the site's design I couldn't ask for a shared machine yet to put the site on. So please bear with me in this )
Steps to reproduce the issue (if relevant):
Not relevant in my opinion, but I will gladly provide some details if required
Copy the apache log (if relevant):
[Wed May 10 10:25:42.899126 2017] [mpm_winnt:notice] [pid 6240:tid 396] AH00428: Parent: child process 244 exited with status 255 -- Restarting.
[Wed May 10 10:25:43.202200 2017] [ssl:warn] [pid 6240:tid 396] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Wed May 10 10:25:43.222835 2017] [mpm_winnt:notice] [pid 6240:tid 396] AH00455: Apache/2.4.23 (Win64) OpenSSL/1.0.2h PHP/5.6.30 configured -- resuming normal operations
[Wed May 10 10:25:43.222835 2017] [mpm_winnt:notice] [pid 6240:tid 396] AH00456: Apache Lounge VC11 Server built: Jul 8 2016 11:33:36
[Wed May 10 10:25:43.222835 2017] [core:notice] [pid 6240:tid 396] AH00094: Command line: 'C:\\Bitnami\\WAMPST~1.30-\\apache2\\bin\\httpd.exe -d C:/Bitnami/wampstack-5.6.30-2/apache2 -f C:\\Bitnami\\WAMPST~1.30-\\apache2\\conf\\httpd.conf'
[Wed May 10 10:25:43.238477 2017] [mpm_winnt:notice] [pid 6240:tid 396] AH00418: Parent: Created child process 5308
[Wed May 10 10:25:44.202668 2017] [ssl:warn] [pid 5308:tid 284] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Wed May 10 10:25:44.452693 2017] [ssl:warn] [pid 5308:tid 284] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Wed May 10 10:25:44.468320 2017] [mpm_winnt:notice] [pid 5308:tid 284] AH00354: Child: Starting 64 worker threads.