| ';
}
```
* However, the input also gets run through the wordpress wp_kses_post() function,
which in my case was removing my iframe markup even though I had allowed iframes
in the above filter. I ended up having to also add iframe to the allowed tags
for the wp_kses function by doing the following:
* ```
add_filter('wp_kses_allowed_html', 'om_allow_iframes');
function om_allow_iframes( $allowedtags ) {
$allowedtags['iframe'] = array(
'src' => array(),
'height' => array(),
'width' => array(),
'frameborder' => array(),
'allowfullscreen' => array(),
);
return $allowedtags;
}
```
* You might have to do the same for the table tags, not sure.
* Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
In reply to: [[Zerif Lite] Zerif Lite child theme](https://wordpress.org/support/topic/zerif-lite-child-theme/)
* [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [10 years, 8 months ago](https://wordpress.org/support/topic/zerif-lite-child-theme/#post-5915417)
* Thanks Ericmulder, that hook worked, except now the parent stylesheet is enqueued
after my child theme stylesheet. I’m using my child theme css to overwrite a
bunch of styles, so I want to have it enqueued after the parent theme stylesheet.
* To do so, I deregistered the child sheet stylesheet and then re-registered /
enqueued it after like below:
* ```
// enqueue the parent theme stylesheet with a low priority so it loads after bootstrap CSS
add_action( 'wp_enqueue_scripts', 'theme_enqueue_styles', 11 );
function theme_enqueue_styles() {
wp_enqueue_style( 'parent-style', get_template_directory_uri() . '/style.css' );
}
add_action( 'wp_enqueue_scripts', 'child_theme_enqueue_styles', 12 );
function child_theme_enqueue_styles() {
// remove child theme style sheet from being called before parent stylesheet
wp_deregister_style( 'zerif_style' );
// enqueue child theme style sheet again
wp_register_style( 'my_child_theme_style',
get_stylesheet_directory_uri() . '/style.css',
array(),
null,
'all' );
wp_enqueue_style( 'my_child_theme_style' );
}
```
* Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
In
reply to: [[Advanced Custom Fields (ACF®)] Getting wp_richedit_pre is deprecated since version 4.3! notice with wywisyg](https://wordpress.org/support/topic/getting-wp_richedit_pre-is-deprecated-since-version-43-notice-with-wywisyg/)
* Thread Starter [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [10 years, 10 months ago](https://wordpress.org/support/topic/getting-wp_richedit_pre-is-deprecated-since-version-43-notice-with-wywisyg/#post-6452446)
* Hmmm. Seems to go away when I simply delete the wysiwyg fields generating the
error and recreate them. So I suppose it’s fixed now.
* Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
In reply to: [Googlebot cannot access CSS and JS files](https://wordpress.org/support/topic/googlebot-cannot-access-css-and-js-files/)
* [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [10 years, 11 months ago](https://wordpress.org/support/topic/googlebot-cannot-access-css-and-js-files/page/3/#post-6374367)
* > I disagree with this. You definitely want to block directories you don’t want
> crawled regularly or more importantly, indexed.
* Apparently WordPress no-indexes files in the wp-admin directory by default, so
they won’t be crawled even if the directory isn’t blocked in the robots.txt
* From Yoast:
* > WordPress has a robots meta x-http header on the admin pages that prevents
> search engines from showing these pages in the search results, a much cleaner
> solution.
* In other words, I think we’re good to leave the robots.txt file blank.
* Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
In reply to: [Googlebot cannot access CSS and JS files](https://wordpress.org/support/topic/googlebot-cannot-access-css-and-js-files/)
* [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [10 years, 11 months ago](https://wordpress.org/support/topic/googlebot-cannot-access-css-and-js-files/page/3/#post-6374343)
* I, too, received this notification for dozens of my sites.
* Most of the sites were completely up to date and only the /wp-admin/ was being
blocked in the robots.txt, which is something WordPress appears to do be default
and isn’t related to any plugin.
* When I used the Fetch and Render tool in GWT and saw what Google has rendered,
Google bot was being blocked from accessing some scripts under /wp-admin/, with
admin-ajax being the main culprit.
* As a temporary fix, I just removed the /wp-admin/ disallow entirely using the
below filter:
* ```
add_filter( 'robots_txt', 'om_remove_wp_admin_block', 10, 2 );
function om_remove_wp_admin_block($output, $public) {
if ( !$public ) {
return $output;
} else {
$output = "";
return $output;
}
}
```
* I then reran the Fetch and Render in GWT and my site passed without any issues.
* According to Yoast, removing the wp-admin block shouldn’t be a problem either:
[https://yoast.com/wordpress-robots-txt-example/#updates](https://yoast.com/wordpress-robots-txt-example/#updates)
* Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
In
reply to: [[Simple Instagram] Updating to the latest version broke my site](https://wordpress.org/support/topic/updating-to-the-latest-version-broke-my-site/)
* Thread Starter [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [11 years, 1 month ago](https://wordpress.org/support/topic/updating-to-the-latest-version-broke-my-site/#post-6198599)
* Much better, everything works now with version 2.0.2
* One minor annoyance, but I did have to reauthorize instagram in your plugin after
upgrading. Not sure if you can do anything about that.
* Anyway, thanks and great plugin!
* Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
In reply to:
[[Advanced Custom Fields (ACF®)] A definite must-have plugin](https://wordpress.org/support/topic/a-definite-must-have-plugin/)
* Thread Starter [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [11 years, 3 months ago](https://wordpress.org/support/topic/a-definite-must-have-plugin/#post-7945668)
* Gravity Forms, Wordfence, and WordPress SEO for Yoast.
* Then WooCommerce if there’s any ecommerce.
* Those 5 plugins are generally enough for 90% of my clients and websites.
* Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
In
reply to: [[Gravity PDF] Example templates not working – getting WP debug error](https://wordpress.org/support/topic/example-templates-not-working-getting-wp-debug-error/)
* Thread Starter [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [11 years, 4 months ago](https://wordpress.org/support/topic/example-templates-not-working-getting-wp-debug-error/#post-5811450)
* Duurrr, I just upgraded gravity forms from 1.8 to 1.9.1.2 and everything works
fine now.
* Thanks for the help. I’ll close this out now.
* Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
In
reply to: [[Gravity PDF] Example templates not working – getting WP debug error](https://wordpress.org/support/topic/example-templates-not-working-getting-wp-debug-error/)
* Thread Starter [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [11 years, 4 months ago](https://wordpress.org/support/topic/example-templates-not-working-getting-wp-debug-error/#post-5811445)
* I just tested it another server with PHP 5.4 and everything appears to be working
fine.
* Can I assume this issue is caused by the old php version and if so then what
can be done about it? (besides upgrading PHP which sadly isn’t an option)
* Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
In
reply to: [[Gravity Forms: Post Updates] Problem showing edit form based on edit link](https://wordpress.org/support/topic/problem-showing-edit-form-based-on-edit-link/)
* Thread Starter [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [11 years, 6 months ago](https://wordpress.org/support/topic/problem-showing-edit-form-based-on-edit-link/#post-5584683)
* Ok, it seems that the generated nonce is user specific and without it appended,
the form won’t contain any data. So we’re good here, please ignore my question.
* Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
In
reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] SEO: Bad Check – Can this be removed](https://wordpress.org/support/topic/seo-bad-check-can-this-be-removed/)
* Thread Starter [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [12 years, 1 month ago](https://wordpress.org/support/topic/seo-bad-check-can-this-be-removed/#post-4993498)
* In case anyone has the same problem, my solution was just to hide it via CSS.
* I did this by adding the following to my functions file:
* ```
add_action('admin_head', 'remove_wp_seo_score_title');
function remove_wp_seo_score_title() {
echo '';
}
```
* Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
In
reply to: [[Photo Gallery, Sliders, Proofing and Themes - NextGEN Gallery] Getting titles to appear on Gallery Template in nextgen 2.0](https://wordpress.org/support/topic/getting-titles-to-appear-on-gallery-template-in-nextgen-20/)
* Thread Starter [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [12 years, 9 months ago](https://wordpress.org/support/topic/getting-titles-to-appear-on-gallery-template-in-nextgen-20/#post-4096948)
* Any update on this?
* Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
In
reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Meta descriptions only on 1st page of paginated content](https://wordpress.org/support/topic/meta-descriptions-only-on-1st-page-of-paginated-content/)
* [Ollie Murphy](https://wordpress.org/support/users/omurphy/)
* (@omurphy)
* [12 years, 10 months ago](https://wordpress.org/support/topic/meta-descriptions-only-on-1st-page-of-paginated-content/#post-3205430)
* According to Yoast ([https://twitter.com/yoast/status/372393537771667456](https://twitter.com/yoast/status/372393537771667456)),
this is on purpose. It’s to prevent duplicate meta descriptions in Google Webmaster
tools.
* So, even though MOZ is marking this as a problem, I guess it’s not an issue from
an SEO point of view.
Viewing 15 replies - 1 through 15 (of 19 total)
1 [2](https://wordpress.org/support/users/omurphy/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/omurphy/replies/page/2/?output_format=md) |
|---|