Radices
Forum Replies Created
-
Forum: Plugins
In reply to: [Elevate SEO] Private pages in sitemap.Yes original error is fixed.
Not sure how to see them in Elevate?
Forum: Plugins
In reply to: [Elevate SEO] Private pages in sitemap.Ok it regenerated when I updated. I also tried the top menu option after deleting a page. Checked the other crawl errors and the rest are due to pages that are marked-up as no-index but being submitted in the sitemaps. These pages are from easy digital downloads cart pages. Not sure how much google cares about that.
Yoast is no longer supporting installs on < WP 5.0 so alternatives are good to have.
Thanks for the fix
Forum: Plugins
In reply to: [Elevate SEO] Private pages in sitemap.Sure. Can you tell me how the site map creation is triggered. Will it be recreated upon the update or does something else need to happen ie Cron
Forum: Plugins
In reply to: [Elevate SEO] Private pages in sitemap.<url> <loc>https://gtmanagement.com/mijireh-secure-checkout/</loc> <priority>0.8</priority> <lastmod>2014-03-28</lastmod> <changefreq>weekly</changefreq> </url>Forum: Plugins
In reply to: [Elevate SEO] Robots.txtJust to be clear that code ends up falling back to the last function and outputs the two lines whether I have a robots.txt file or not. This prevents the 400 error but in any case the plugins functionality (and WordPress’s) is lost as far as robots.txt is concerned.
Forum: Plugins
In reply to: [Elevate SEO] Robots.txtOk Solved it … well found the answer here: https://codex.wordpress.org/Nginx
Added this code to the nginx .conf file for the domain. /etc/nginx/conf.d/vhosts
# robots.txt fallback to index.php location = /robots.txt { # Some WordPress plugin gererate robots.txt file allow all; try_files $uri $uri/ /index.php?$args @robots; access_log off; log_not_found off; } # additional fallback if robots.txt doesn't exist location @robots { return 200 "User-agent: *\nDisallow: /wp-admin/\nAllow: /wp-admin/admin-ajax.php\n"; }Forum: Plugins
In reply to: [Elevate SEO] Robots.txtI can’t find anything definitive in the logs. Looks like the requested url is \@backend.
Can’t see if that comes from nginx or WordPress.Coming from nginx and maybe SSL related.I can create a robots.txt in 30 seconds and it works fine so I’m fighting the urge to jump down this rabbit hole 🙂 Thanks for showing me the hook I was unaware of it.
[root@srv1 ~]# varnishlog * << BeReq >> 71 - Begin bereq 70 fetch - Timestamp Start: 1550778704.265987 0.000000 0.000000 - BereqMethod GET - BereqURL \@backend - BereqProtocol HTTP/1.0 - BereqHeader Host: gtmanagement.com- This reply was modified 7 years, 2 months ago by Radices.
Forum: Plugins
In reply to: [Elevate SEO] Robots.txtCentos 7
nginx>varnish>apache>php-fpm 7.3gtmanagement using WordPress 5.0.3
jethosted using ClassicPress RC1So looks like a permissions issue to hit robots.txt from the backend.
- This reply was modified 7 years, 2 months ago by Radices.
Forum: Plugins
In reply to: [Elevate SEO] Robots.txthttps://jethosted.ca/
https://gtmanagement.com/Tried with no plugins active but run 35 in production for gt site. Changed theme to 2019.
.htaccess file is changed as is wp-configAlso tried turning on debug log.
It doesn’t appear to be working either, can’t find the file, not clear where its supposed to live.Found the file in the plugins folder …Would be nice that info was in the help bubble.Manually created a Robots.txt file to see if it would get written to and it does not change at all upon saving options.
PHP FPM 7.3
Forum: Fixing WordPress
In reply to: 5.01 breaks website with php pages5.0.1 is a security release and is known to break some things. Look here for more details.
1https://make.wordpress.org/core/2018/12/13/backwards-compatibility-breaks-in-5-0-1/
Forum: Fixing WordPress
In reply to: Can’t upload theme on local serverIt sounds like a permissions problem on the server. Folders should be set to 0755 and files to 0644. Talk to your host if you do not have direct access.
Forum: Fixing WordPress
In reply to: variable mismatchhttps://make.wordpress.org/core/2018/12/13/backwards-compatibility-breaks-in-5-0-1/
Form element no longer passes KSES
Prior to 5.0.1, the $allowedposttags array contained an entry for the <form> element and some of its attributes. Because of that, Contributors and Authors could use it in posts.The element was removed in 5.0.1, except for situations where a plugin has explicitly registered input or select fields via the wp_kses_allowed_html filter. If a Contributor or Author includes <form> in their post, it will be removed when the post is saved. It will also be stripped from arbitrary content that plugins pass to wp_kses_post() or wp_kses_allowed_html( ‘post’ ).
If a plugin author wants to restore the original behavior, they will need to add form, input or select tags via wp_kses_allowed_html. Please exercise caution when doing so, because this could re-introduce a vulnerability. Make sure only trusted users are allowed to add <form> tags.
Forum: Fixing WordPress
In reply to: Unable to post new pages since WP 5.0 updatesHave you tried the classic editor plugin?
Forum: Fixing WordPress
In reply to: Assigning Templates to Pages in WP 5.0Templates are theme based. What theme are you using? Under the Page Attributes sidebar my theme is showing templates.
- This reply was modified 7 years, 4 months ago by Radices.
Forum: Fixing WordPress
In reply to: Creating a splash pageThat would work!