Carlos Fernando Casta?eda Castro
Forum Replies Created
-
En la sección apariencia solo aparece el botón ?guardar cambios?
Stop the presses.
I did the following, deactivated and de-installed jetpack.After that, I reinstalled it, reloaded all the previous configurations that I already had configured.
And the miracle happened. The right bar was properly in place. https://drive.google.com/file/d/1lcfKU7VpirWiNOjIiT_zDCJ3sGAiVI8z/view?usp=sharing
Your last contribution was very illustrative since it made me wonder what would happen if I uninstalled and reinstalled Jetpack.
Thanks for your help.
- This reply was modified 4 years, 1 month ago by Carlos Fernando Casta?eda Castro.
Good evening, thanks for replying. I start at the end.
I tried Twenty Sixteen theme, I attach 2 images and the problem persists.
https://drive.google.com/file/d/1hdK7IJR_gItDXSKwChEO02jUyRPBviS4/view?usp=sharing
https://drive.google.com/file/d/1U7kZXwwyLIKpxp1hXO49pVxjDZtgpYFs/view?usp=sharingAs I mentioned, they are only activated for the Jetpack and official AMP tests, I attach 2 images, without any active cache plugin.
https://drive.google.com/file/d/10MZxLV-uVhBDj0VGosEOeBq_H2OIjDSk/view?usp=sharing
https://drive.google.com/file/d/1DrhLhTGT-BdsP6f0GJBWSSO1pNiot8Hl/view?usp=sharingI repeat when the Jetpack share button appears the error, if I deactivate the share button the error disappears.
As I repeat, when reviewing the code in the sharing-service.php file, I found that line 930 looks like this: $ sharing_content. = ‘</div> </div> </div>’; With that appears the problem of the left bar.
Now, on that same line 930 I left it like this: $sharing_content.= ‘</div>’; that is, I removed 2 DIV closures and that way it works correctly, both in the version without AMP and with the AMP version.
When Jetpack’s share buttons are active and the official AMP is active, the full-screen right sidebar pops out of place and goes to the bottom of the screen.
Wrong view with the right bar (right sidebar) displaced due to active jetpack share buttons. https://drive.google.com/file/d/1QbQAfYurQ8W8QKxcnjeXIwYsMcSaa9R0/view?usp=sharing
On the other hand, if I deactivate the Jetpack share buttons they are deactivated and the official AMP remains active, then the right sidebar remains in the correct place.
Right view with right bar (right sidebar) with jetpack share buttons off and AMP active.
https://drive.google.com/file/d/1IU0xbVBFfqPnJ_zRelUKl3BWmMHT–7S/view?usp=sharingOnly jetpack and official AMP are active in the tests.
I have tried it with 3 different themes with the same result.
I can’t test Twenty Nineteen because it doesn’t have a right sidebar.Reviewing the code in the sharing-service.php file, I found that line 930 looks like this: $sharing_content .= ‘</div></div></div>’; With that, the left bar problem appears.
Now, on that same line 930 I left it like this: $sharing_content .= ‘</div></div></div>’; That way, it works correctly, both in the version without AMP and with the AMP version.
Forum: Themes and Templates
In reply to: [Wellington] AMP and sidebarI found the error.
The error occurs with active jetpack and its share buttons with Wellington theme and AMP.
If the jetpack share buttons are disabled the sidebar works fine in the theme together with AMP.
- This reply was modified 4 years, 6 months ago by Carlos Fernando Casta?eda Castro.
Forum: Themes and Templates
In reply to: [Wellington] New menuthank you very much for your reply. The solution you propose is not viable, since I want to wrap the menu tag and not the link. the reason for wrapping the tag is to place the corresponding schema tag. Indeed, there is another way to do it and it is that when putting the menu tag in the menu configuration, add the <span> to it, but that solution is not very clean, since, in the case of a complex menu, the user would have I have to modify each of the links by hand, when there is link_before and link_after, to do so.
Forum: Plugins
In reply to: [Yoast SEO] main-sitemap.xsl – error 500No resolver.Michael Tina wrote:
After a bit of further digging, we were able to create and confirm that this is indeed an issue with the main sitemap as the root causing fatal errors, and is in v14.6.1 of Yoast SEO for WordPress. Our developers are aware of the issue and will include a fix to this. We apologize for any inconvenience.
Forum: Plugins
In reply to: [Yoast SEO] main-sitemap.xsl – error 5001. Yes, it only started with the current version of Yoast 14.6.1.
2. No.Forum: Plugins
In reply to: [Yoast SEO] main-sitemap.xsl – error 500It is right.
With all browsers it gives 500 error about the * .xls fileForum: Plugins
In reply to: [Yoast SEO] main-sitemap.xsl – error 5007 years ago I had WordPress configured that way and with that configuration I used the Yoast sitemap. If you can’t modify, for that specific case, please use the native WordPress sitemap that will come out in the next update, in the meantime please use the Jetpack sitemap.
Forum: Plugins
In reply to: [Yoast SEO] main-sitemap.xsl – error 500No. If I change the address for both then it works.
The server configuration is:
WordPress Address (URL):
https: // localhost / wordpress
and the site address (URL) is: https: // localhost. It does not work like this. the * .xls file failsForum: Plugins
In reply to: [Yoast SEO] main-sitemap.xsl – error 5001.If Address (URL): https://localhost/ wordpress and Site Address (URL) is: https:// localhost/wordpress. There it works.
2. WordPress 5.4.2.
3. Yoast Versión 14.6.1.
4. Clear chache and developer mode.
5. Sitemap of jetpack active temporaly.Forum: Plugins
In reply to: [Yoast SEO] main-sitemap.xsl – error 500The server configuration is:
WordPress Address (URL):
https: // localhost / wordpress
and Site Address (URL) is: https: // localhost
It does not work like this.If Address (URL):
https: // localhost / wordpress
and Site Address (URL) is: https: // localhost / wordpress
There it works.In the meantime I have disabled the option.
Forum: Plugins
In reply to: [Yoast SEO] main-sitemap.xsl – error 500[26-Jul-2020 22:02:55 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_contents() on null in /home/politi17/public_html/wordpress/wp-content/plugins/wordpress-seo/inc/sitemaps/class-sitemaps.php:440
Stack trace:
#0 /home/politi17/public_html/wordpress/wp-content/plugins/wordpress-seo/inc/sitemaps/class-sitemaps.php(249): WPSEO_Sitemaps->xsl_output(‘main’)
#1 /home/politi17/public_html/wordpress/wp-includes/class-wp-hook.php(287): WPSEO_Sitemaps->redirect(Object(WP_Query))
#2 /home/politi17/public_html/wordpress/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(”, Array)
#3 /home/politi17/public_html/wordpress/wp-includes/plugin.php(544): WP_Hook->do_action(Array)
#4 /home/politi17/public_html/wordpress/wp-includes/class-wp-query.php(1768): do_action_ref_array(‘pre_get_posts’, Array)
#5 /home/politi17/public_html/wordpress/wp-includes/class-wp-query.php(3432): WP_Query->get_posts()
#6 /home/politi17/public_html/wordpress/wp-includes/class-wp.php(624): WP_Query->query(Array)
#7 /home/politi17/public_html/wordpress/wp-includes in /home/politi17/public_html/wordpress/wp-content/plugins/wordpress-seo/inc/sitemaps/class-sitemaps.php on line 440Forum: Plugins
In reply to: [Yoast SEO] main-sitemap.xsl – error 500Your assessment is not correct, if observing, Failed to load resource: the server responded with a status of 500 () main-sitemap.xsl
- This reply was modified 4 years, 7 months ago by Carlos Fernando Casta?eda Castro.