Comparativa de Bancos

Hello

the do_shortcodefunction should be placed within the loopshortcode.

I.e. when you want that a shortcode correctly displays the content of a “child” shortcode you have to put the do_shortcode.

These are not your current functions but to explain it.

function loop(){
return do_shortcode( $content );
}

BR

Nice. Another thing I just noticed.

I am making my first tests with the plugin and this
[loop type=”post” count=”3″ ][content][/loop]

In a current post with this example content

paragraph 1
[loop type=”post” count=”3″ ][content][/loop]
paragraph 2
paragraph 3

The plugin is displaying the loop content at the end of paragraph3 and not in the middle.

May be you should add “do_shortcode($out)” when returning the content in the “content” shortcode.

BR

Having the same problems here with twenty fourteen and just your plugin enabled so it has to be your plugin…

Strict Standards: Redefining already defined constructor for class PCS_Content_Widget in wp-content/plugins/post-content-shortcodes/class-post-content-widgets.php on line 181

Strict Standards: Redefining already defined constructor for class PCS_List_Widget in wp-content/plugins/post-content-shortcodes/class-post-content-widgets.php on line 245

Strict Standards: Declaration of PCS_Widget::update() should be compatible with WP_Widget::update($new_instance, $old_instance) in wp-content/plugins/post-content-shortcodes/class-post-content-widgets.php on line 13

Strict Standards: Declaration of PCS_Widget::form() should be compatible with WP_Widget::form($instance) in wp-content/plugins/post-content-shortcodes/class-post-content-widgets.php on line 13

Strict Standards: Declaration of PCS_Content_Widget::form() should be compatible with PCS_Widget::form() in wp-content/plugins/post-content-shortcodes/class-post-content-widgets.php on line 176

Strict Standards: Declaration of PCS_Content_Widget::update() should be compatible with PCS_Widget::update() in wp-content/plugins/post-content-shortcodes/class-post-content-widgets.php on line 176

Strict Standards: Declaration of PCS_List_Widget::form() should be compatible with PCS_Widget::form() in wp-content/plugins/post-content-shortcodes/class-post-content-widgets.php on line 240

Strict Standards: Declaration of PCS_List_Widget::update() should be compatible with PCS_Widget::update() in wp-content/plugins/post-content-shortcodes/class-post-content-widgets.php on line 240

I have been checking it and really dont know. I can post here all my emails but just happens with CPTUI.

Anyhow, what I have done is using your plugin for generating the code and then using it directly in a custom plugin and it is working fine.

I dont want you to waste more time with this issue since it seems to be an strange behaviour.

Thansk a lot for your suppport!

Hello

Here the pasted code

https://pastebin.com/GNUpS4ug

BTW, I am also using https://www.ads-software.com/plugins/gd-taxonomies-tools/ that is the one I wanted to replace by yours and havent removed it yet.

But I have no problem with EDD and GD, it is just when installing CPTUI.

BR

Hello all,

yes, it is just happening with EDD (afaik).
I have been working with EDD and another plugin for CPT for a long time and no problem.

I wanted to give your plugin a try and then EDD custom posts disappear from backend and they are also not accesible from frontend.

They stopped appearing in the admin sidebar, although the plugin is still active.

If I disable CPT UI then everything is working fine again.

Thanks

Nice, can you email me?

contacto at my name without spaces dot com

Thanks

Hello,

I have done it but still having the same problem.

Anyhow, what I have done is to run it in my local wamp and it is working fine. It is not the same environment as live but enough to have an idea of the performance of each plugin.

Thanks a lot for trying!

Hello

I deactivated W3TotalCache and still the same issue.

I have XCache in the server with nginx.

This is my system info, is it enough?
https://pastebin.com/7MHpBKs0

BR

Hello

you can go to your database and delete or rename this entry
Yoast_Google_Analytics
in wp_options table.

It will work but you will need to reconfigure again the plugin.
The configuration can be guessed reading the content of Yoast_Google_Analytics. If you rename it, you can do it and then delete the renamed one.

BR

Same problem in my site with this message

( ! ) SCREAM: Error suppression ignored for
( ! ) Fatal error: Cannot use string offset as an array in \wp-content\plugins\google-analytics-for-wordpress\admin\class-admin.php on line 342
Call Stack
# Time Memory Function Location
1 0.0038 845896 {main}( ) ..\options-general.php:0
2 0.0058 963328 require_once( ‘,,,\wp-admin\admin.php’ ) ..\options-general.php:10
3 0.7639 45143952 do_action( ) ..\admin.php:151
4 0.7640 45145472 call_user_func_array ( ) ..\plugin.php:406
5 0.7640 45145504 GA_Admin->config_page( ) ..\plugin.php:406

and also someone else having the same issue.
https://www.ads-software.com/support/topic/fatal-error-when-i-hit-settings-button?replies=1

I thought it was some kind of conflict with jquery or something but I have deactivated every plugin I have, left functions.php blank and wp-config.php to its minimum so it has to be something else.

I have the same problem also working in local so it has to be something with the database, maybe with people that has previously logged in with GA credentials.

We cant do anything now since the settings is empty.

Thanks

you can try adding something like for your yoast_tracking class

delete_action( ‘my_task_hook’, ‘my_task_deactivate’ );
// clean the scheduler
function my_task_deactivate() {

wp_clear_scheduled_hook( ‘my_task_hook’ );
}

same error here

…public_html/wp-content/plugins/bbpress-private-replies/bbp-private-replies.php (164)
in BBP_Private_Replies::hide_reply called at ? (?)

Now in newrelic

Error message

Error: Cannot use string offset as an array

Stack trace

…c_html/wp-content/plugins/google-analytics-for-wordpress/admin/class-admin.php (344)
in GA_Admin::config_page called at ? (?)

I also have the same problem after upgrading to 4.3.1