apg1912

No, I haven’t disabled all plugins and so I guess that is my next step. Because it was a WP function in misc.php in wp-admin, I didn’t think other plugins could mess with that because it’s in the WP admin space.

The function is ‘_wp_privacy_settings_filter_draft_page_titles( $title, $page )’

and the statement causing the error begins:
if ( ‘draft’ === $page->post_status && ‘privacy’ === get_current_screen()->id ) ….

post_status is undeclared.

The staging site is on a hosting company site served by Linux.

• This reply was modified 4 years, 2 months ago by apg1912.
• This reply was modified 4 years, 2 months ago by apg1912.

Ok, thank you for that. At least I can now look for alternative solutions rather than trying to work out why what I currently have is not working.

Many thanks.

Many thanks for your reply.

I am using the following 2 widgets in the sidebar. They are not 3rd party and so I guess they come with either Storefront or WooCommerce.

It is NOT the WooCommerce Product Search premium plugin. I have been contemplating that one, but can’t really see that it gives me much more than I’m getting in the default one I see in my widgets listing that is worth paying money for.

Does this mean that my sidebar might actually by displaying but there are no ‘valid’ widgets to display in it as it is being used on a standard page (ie not product or category related)?

I am wanting to put up a welcome home page but would like visitors to quickly and easily be able to select products to view by category and/or colour.

Product Categories: Product Categories (with following checkboxes)
– Show as dropdown
– Show product counts
– Show hierarchy
– Only show children of the current category
– Hide empty categories

Filter Products by Attribute: Select by Colour (with following dropdowns)
– Attribute type
– Display type
– Query Type

• This reply was modified 4 years, 2 months ago by apg1912.
• This reply was modified 4 years, 2 months ago by apg1912.
• This reply was modified 4 years, 2 months ago by apg1912.
• This reply was modified 4 years, 2 months ago by apg1912.
• This reply was modified 4 years, 2 months ago by apg1912.
• This reply was modified 4 years, 2 months ago by apg1912.
• This reply was modified 4 years, 2 months ago by apg1912.
• This reply was modified 4 years, 2 months ago by apg1912.

Fixed. There was reference to $product->short_description in some code in the functions.php file and so I changed it to $product->get_short_description().

• This reply was modified 5 years ago by apg1912.

I meet the version requirements for 3.9 and so I don’t think there are compatibility issues. I’m pretty sure if I were to turn on debug for my live site (3.7), those notices would appear. I guess I’ll just have to research this one myself and try and figure out what is going on.

I’ve turned debug off on the staging site, and the notice goes away. I’m presuming then that it will appear on the live site if I turn debugging on, indicating this is not an upgrade issue.

I would still like to know how to fix it though and so any help would be appreciated.

Thanks for the reply. I use about half a dozen plugins that are related to WooCommerce and so I guess one of those is upset about ‘losing’ WooCommerce.

I spoke to the hosting company about it, and as a result, I set up a staging site and WooCommerce was updated via WP-CLI, and so that is another option.

Now, I just need to give it a good testing before updating the live site.

By getting the website to reference a folder called ‘styles’ instead of ‘css’ containing the same files, the site works again. I had the same problem with a folder called ‘images’, and so I created a new folder at the same level called ‘imgs’, copied in the contents of ‘images’, and that then worked as well.

I have looked at the folder properties, permissions, etc for a long time, and so see no differences between them and so I am at a loss to explain any of this other than some folder corruption that has somehow occurred.

I thought I’d add the following as it may be relevant.

I created a new folder called ‘demo’ under ‘assets’ and copied in the contents of the ‘css’ folder.

Typing in the following url worked!
localhost/chfootball/wp-content/themes/oceanwp-child/assets/demo/demo.css

So, I deleted the ‘css’ folder, and renamed ‘demo’ to ‘css’. And guess what? It failed again! Is there something special about the directory name ‘css’?

• This reply was modified 5 years, 1 month ago by apg1912.

Thanks for the suggestions. There is no SSL configuration on this PC. I decided to follow up on your directory file owner suggestion.

I moved the demo.css file into every folder leading back to the route.

localhost/chfootball/demo.css
localhost/chfootball/wp-content/demo.css
localhost/chfootball/wp-content/themes/demo.css
localhost/chfootball/wp-content/themes/oceanwp-child/demo.css
localhost/chfootball/wp-content/themes/oceanwp-child/assets/demo.css

All the above display the file okay. However, as soon as I issue the following:

localhost/chfootball/wp-content/themes/oceanwp-child/assets/css/demo.css

I get the Site Not Found due to 301 redirect to https.

Thing is, I can see no difference in the permissions of the css directory compared to the ones above it. I must be missing something and so I will continue to follow up this line of thought.

All the permissions are inherited all the way down from C:/ so there must be something else at play.

• This reply was modified 5 years, 1 month ago by apg1912.
• This reply was modified 5 years, 1 month ago by apg1912.

That is the problem. The set up outside of WordPress is identical other than the names of the folders. As far as I can see, .htaccess is the only file that can be used for customisation, and it is not doing anything differently in these cases. It all points to Apache for me but I have no idea where this 301 redirect is originating.

.htaccess

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /chfootball/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /chfootball/index.php [L]
</IfModule>

Thanks for the reply, but I’ve checked the .htaccess files for both projects and they are identical, except for the fact one references ‘chfootball’ and the other references ‘target’. The commands in each are the same though.

• This reply was modified 5 years, 1 month ago by apg1912.

I re-created the project with NO plugins.

If I place and reference the ‘frontpage.css’ in the site’s root folder it is successfully accessed. If I try and reference it from ‘wp-content/themes/oceanwp-child/assets/css’, I still get the refused connection message.

Why should a path make a difference? I have absolutely no idea!

• This reply was modified 5 years, 1 month ago by apg1912.
• This reply was modified 5 years, 1 month ago by apg1912.

Thanks for the reply.
1. I don’t use WooCommerce on this site. I am going to try disabling all plugins though, just in case…

2. I’ll try that code to see if it helps.

3. Didn’t know there was such a tool. I’ll definitely install it.

4. I’ll try the theme idea just to rule that one out as the site requires the OceanWP theme.

5. I was just going to edit the relevant WP table entries to do this, but I guess it would give me a good reason to become familiar with this tool.

I raised this issue on stackoverflow and as my Apache files have no apparent entries to cause this, it is being suggested my app is doing it. If that is the case, then it must be a WP issue, possibly caused by a plugin.