nadodi

Thanks @cristianbarbu. Tried different rollbacks, but nothing worked.

What worked finally is updating One Page Express. The error message on the customizer was a bit more specific. It said “to customize an inside page, upgrade to the pro version.” We were using a different page as home page. Once we switched that to the default Front Page, it worked fine. Looks like the upgrade may have enabled something that was working differently earlier – we could customize any page.

Hope that helps someone else who might run into this issue.

The issue has been fixed. The css for a previous element was missing a curly bracket. It was deleted by mistake during copy/paste.

Thank you.

• This reply was modified 3 years, 5 months ago by nadodi.

Thanks @hchouhan – it is the border bottom color that we are trying to change from red to a golden brown. Tried the !important tag for the border bottom color, but not working. That line still resolves to red.

Fixed – tried to edit a header element. That seems to bring all the sections back.

Using 3.7, but Authors do not have access to shortcodes.

gn_themes: thanks for the great plugin.

Those were the dreaded UTF Byte Order Marks (BOM).

To inspect your file for BOM (note you have to do each include file separately):
https://people.w3.org/rishida/utils/bomtester/

To delete it using Notepad++:
Open the php file using Notepad++ … now, you won’t even see the BOM marks there, BUT it can remove them. Do this. Your file is most likely UTF-8. Go to Format, and select “Encode in ANSI”. Then go to Format again, and select UTF-8 without BOM. Save your file. (from Joomlapolis)

Hello All,

This issue has been resolved. In case you are interested in knowing how:

There seems to be an issue with how virtual directories are setup. After struggling for entirely too long to try to fix it, we decided to pull the home page into WordPress. Here is how we did it:

Splash Home Page
1. Create a new blank page (page 1) in WordPress. Set this to be the front page in WP Admin > Options > Reading.
2. Move welcome.php from root to theme folder
3. Use an if statement in page.php to pull or include welcome.php whenever page 1 is called.

Result – splash page is inside WP and works fine (see home page). This gives us a blank page to create the splash page from, thus providing complete independence in layout, structure, etc. Would love to hear thoughts on whether this method has any performance implications.

Blog Post Listing Page
WordPress now thinks that the splash page is the index page. But the site also needs to get it to serve the usual list of blog posts in a page, a task done by the index.php page earlier. Here is how that was done:

1. Create another blank page (page 2) in WordPress. Set this to be posts page in WP Admin > Options > Reading.
2. Copy code from index.php in the theme folder to create a new php file called file1.php.
3. Use an if statement in page.php to pull or include file1.php whenever page 2 is called.

Result – new page lists all the posts as index.php did earlier (see blog page). We are within the theme’s header, sidebar, footer, etc., for other components of the page.

Not sure if this method is optimal to get to a completely blank slate for the home page. But it is doing what we want the site to do. So, we are happy to let it be. ??

If you have a question or need more details on any of the above, please leave a note here.

Hi Moshu,

Thanks for persisting in the hunt for the issue.

I used WP codex instructions to create the static front page for WP and to display it using htaccess. It worked fine until the move last night to DreamHost.

The home page is a mix of static and dynamic content. We needed the wp-blog-header to pull dynamic content – WP Posts.

Hope that sheds more light.

The home page is a completely different look and feel from the site. The reading panel does not pull in pages outside of WP to be set as static home page. This is the reason why we had to go the htaccess route.

Moshu, thanks for your response. The URL looks for welcome.php first. This is set to be called prior to index.php via htaccess.

Does that help?