Anton Timmermans
Forum Replies Created
-
We’ve just released 4.2.1 which resolves this issue.
Hello Joel,
These <yoastmark> tags are inserted when using the highlighting feature of the plugin. The little eye you can use to mark our readability advice inside the text. If they end up in your alt tags then the code added these tags there on accident. We try to err on the side of caution here, but it might go wrong sometimes.
Could you create an issue on our GitHub? We have a guide on how to create a GitHub issue. Things that really help tracking this bug is specific content that you can reproduce it with. For example, the content before and after there are <yoastmark> tags in the content.
Anton
- This reply was modified 9 years, 5 months ago by Anton Timmermans.
Forum: Plugins
In reply to: [Content Blocks (Custom Post Widget)] Use the loop in the widgetThe actual point where it is going wrong is when using a social media plugin.
The social media plugin uses the
the_contentfilter to add the social media buttons. In the code for adding the social media buttons there is code comparable like this:if ( is_page() ) { // Display social media buttons }The problems occurs when having a sidebar on that page that has the custom post widget in it.
the_contentfilter is called when displaying the custom post but because the global$postvariable is still set to a page object (the page we are on) the plugin thinks it should display the social media buttons at the end of the_content filter.I don’t think the social media plugin is doing something unreasonable but this might still be a very tricky issue to fix.
For other people dealing with the same issue, I build a workaround to fix this issue. I added a shortcode to all custom blocks named
[hide_social_media_buttons]then I filteredthe_contenttwice, once on priority 9 and once on priority 11. In the first filter I remove the social media button filter if the shortcode is present and in the second filter I re-add the social media button filter if I removed it.Please consider merging this pull request to add a filter to move the menu item to the bottom of the menu.
https://github.com/Yoast/google-analytics-for-wordpress/pull/87Completely agree with this.
Forum: Fixing WordPress
In reply to: Invalid argument supplied for foreach()…..I update the submodule using the following method:
- Remove all the files (except the .git) in the working copy of the submodule.
- Download a new WordPress copy from http://nl.ww.wp.xz.cn.
- Copy all downloaded files in the working copy
- Commit this with a nice commit message, such as “WordPress 3.8.3 -> 3.9”
- Tag this commit with the correct WordPress function, such as “tag -a 3.9”
In a project that has the submodule I then go to the WordPress folder, do “git fetch” and “git checkout 3.9”. It is a completely clean 3.9 installation of WordPress except for the database.
Forum: Fixing WordPress
In reply to: Invalid argument supplied for foreach()…..@samuel, you can achieve the same by just setting WP_DEBUG on false in the wp-config.php.
I can confirm this warning in our development environment. We update WordPress using a submodule with the dutch version of WordPress in it. I only see this error with wp-cli and not in the WordPress admin. Nevertheless I really dislike warnings and notices and would like it if this was fixed.
Guys, I have posted a fix for this in the other thread:
http://ww.wp.xz.cn/support/topic/enable-salesforce-integration-missingForum: Plugins
In reply to: [Gravity Forms Salesforce Add-on] "Enable Salesforce integration" MissingI don’t know anything about salesforce itself, I only implement it for clients. You’d have to email salesforce about it.
Forum: Plugins
In reply to: [Gravity Forms Salesforce Add-on] "Enable Salesforce integration" MissingSoapClient is a build in php object so it has nothing to do with this plugin.
btw. I didn’t fix Salesforce API Add-On because I can’t test it. I only fixes Salesforce Web To Lead plugin.
Forum: Plugins
In reply to: [Gravity Forms Salesforce Add-on] "Enable Salesforce integration" MissingHello,
I had the same problem with the salesforce plugin, the reason it doesn’t work anymore is because gravityforms overhauled the settings page.
If you use a version management system you can use the patch I made:
Patch for settingIf you don’t you can download the full modified plugin here.
I hope this helps you and maybe Zack can use this to make a new version for everyone to download.