kobashicomputing

Why is this not set automatically? Why would you NOT want to use it?

This has nothing to do with validating. It is what WordPress is sending back to the client in response to an improper HTTP METHOD request other than “POST”.

The only piece of information that WordPress has available to it on HTTP server protocol is through:

$_SERVER['SERVER_PROTOCOL']

It must not fake the client out thinking it is something other than what the HTTP server is reporting.

#37863 got re-opened.

Someone beat me to the ticket after obviously having read this very thread.

FTP deletes are slow. Invoking PHP code to delete is slow. More so if you got a theme that has a ton of files to delete.

The quickest way is to SSH and delete the theme folder. It will be done in an instant.

You don’t need to use a plugin. That plugin isn’t going to be useful anyway because looking at its screenshot, it applies CSS rules globally to every HTML object pertaining to a document.

If the document is the home page, search page, archive page, etc. its applies the fonts to all of them. According to the title of this problem, he just wants to apply it to posts.

Fonts are applied through use of CSS.

Some themes have a custom CSS option where you can select or enter in CSS rules. These rules are tied into elements on a web page and differ for each theme.

When you selected the Source Sans Pro Google font, it gave you the standard reference link and the CSS rule to be applied to your HTML elements:

font-family: 'Source Sans Pro', sans-serif;

You need to identify the HTML class that represents a post and apply this CSS rule.

Google Canary is not a stable release of Google Chrome. It is a bleeding edge futuristic version only for experimental purposes.

Please do not report problems with Canary on here and use a supported browser.

Rename the plugin folder located in /wp-content/plugin to pluginold.

See if its a plugin that is causing the problem

Did you rename your .htaccess back to .htaccess?

The .htaccess and index.php files in the /wp folder should be not be modified. The .htaccess should look like this:

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

# END WordPress

The index.php should look like this:

define('WP_USE_THEMES', true);

/** Loads the WordPress Environment and Template */
require( dirname( __FILE__ ) . '/wp-blog-header.php' );

In your Dashboard, Settings | General it should look like this:

WordPress Address (URL): https://sitename.com/wp
Site Address (URL): https://sitename.com

I’ve never had a need for setting these. Where in the instructions link you mentioned above, did you see this? Its not in there. You got these from where?

define('WP_SITEURL','https://www.site.com/directory');
define('WP_HOME','https://www.site.com');

Well the anonymous users would need to be converted to Subscribers. They do that by registering. You could give them temporary access by deciding on a fixed time frame of say, 3 days of access. When they verify themselves by email, their user_registered database field gets set to a date/time.

Knowing that date/time, you could run a cron job that goes in and walks through each User in the database and compare their register time. If it exceeds the time out value (lets say 3 days), then you remove the user out of the database.

Does that sound like a solution?

I’ve never had a need to use a RewriteBase. Try removing that by commenting it out with a hash (#)

In index.php on the root did you do this:
require('./wp/wp-blog-header.php');

Your new login should be:
https://www.site.com/wp/wp-login.php

That’s not an error message string that is in WordPress source code. Your website is up fine. Please mark this as resolved.

Did you read that link that I posted and followed along to see if any of those things were relevant? Please do so. Go through that entire checklist one by one so we can rule out these things.

functions.php is a file packaged with your theme. Most themes have this file to change the behavior of their theme and it is a very important one at that. You will need to go get your theme and copy it to your local computer. Unzip it and then FTP the original functions.php file over to your WordPress site. You should then be back to your original running state before all of this got messed up.

To save you grief in the future, please remember this:
Always make a backup copy of any WordPress file you are going to monkey around with.

I strongly recommend that you go create a local development system running WordPress and your theme on a Windows home computer. Learn with

[link moderated; kep support on this site ]
XAMPP https://make.www.ads-software.com/core/handbook/tutorials/installing-a-local-server/xampp/

before modifying any WordPress files. Make it work on the local development system first before applying any changes directly to a production website. The time that you spend educating yourself in practice will be beneficial in the long running maintenance of your site. I wish I could post this as a pinned topic at the top of this forum to save people grief but I see so many people here modify their production website when they should be testing to make sure it works on a practice website.

Not without recoding the tag cloud widget and tag widget.

The tag widget in the editor would need to be able to associate an icon with a tag term and store that association as a term/file pair.

The tag cloud widget would need to generate HTML for that term/file pair as a img tag wrapped around the anchor tag for the term.