Is anyone using this theme on NGINX?
We’re running Apache/CentOS; but just as an FYI, if WordPress works on your NGINX setup, the theme will work; as a theme is only a collection of style sheets that extend the built-in functions of WordPress.
Typically most developers optimize their site for NGINX using the default theme (e.g., twenty-fourteen), such as issues for Google PageSpeed; then worry about the design as secondary process once the initial WP setup is fully functional.
Thanks Christopher,
You are always very helpful on these forums. If I may ask, I am very confused as to what could be causing this odd rendering issue with columns on the site. Could I send you a private message with link to my site? (It’s a rather large publication so I’d rather not broadcast it here.)
Any insight you might have would be most helpful.
Thanks,
Luca
im running nginx and i havent problems:P . what its your problem?
OK SOLVED!!!! It took me hours…. literally two days of work to narrow this down. Basically there are two database entries that could be put into the WP_OPTIONS table that specifically relate to WordPress Bakery’s Visual Composer.
In my case the two database entries specifically set parameters for the Columns and Rows of WPB’s Visual Composer. Of course components of “Pages” built on this theme use the columns from the Visual Composer.
Deleting those two entries will fix the problem.
This is likely going to be rare for most, unless you are moving directly from Newspaper and had configured some Column and Row functions in the Visual Composer.
I found this by installing a fresh copy of WordPress onto the same NGINX system and comparing the database entries in the old and new instance.
I imported the old database tables into the new one to see which one broke it. Once the options table was imported that caused the rendering issues. Going through hundreds of lines, I found the two responsible.
Easy way to find them is search for an “Option Name” with %___% wild cards in phpmyadmin. Use this specific term “wpb”.
You may get several options listed in rows in the output. The ones with Column and/or Row specifically in the Option Name should be deleted.
Actually you “can” delete all related options but keep the “wpb_js_templates” option as that is common to both a fresh install and a legacy install.
Well, now rendering is fixed for pages and columns and rows work as expected! Yay.
PS: This has nothing to do with NGINX. I confirmed the exact same issue is present on both Apache 2.4.10 with MPM-Prefork and PHP-FPM.
@ bayu
How did you set up the Nginx and php5-fpm, did you install any other stuff like Varnish or Memcached?
Thanks
Hi
I’ve found some useful information in this regard here, it may help: https://www.nginx.com/resources/wiki/start/topics/examples/phpfcgi/ http://www.rackspace.com/knowledge_center/article/installing-nginx-and-php-fpm
Thanks!
There are also some really good articles out there on speeding up your website using Nginx + Varnish for “optimizing WordPress for speed” … don’t have links handy. I looked at that in depth Jan. 2014, ended up sticking with Apache for our little corner of the universe. 🙂
