Forum Replies Created

Viewing 15 replies - 1 through 15 (of 47 total)
  • Thread Starter kaostc

    (@kaostc)

    Thanks!

    Is there any approximation about when the next update will be released (just for information)?

    Best.

    Thread Starter kaostc

    (@kaostc)

    Sorry, you are right, there is a conflict with fusion builder and your plugin. Fusion builder is core part of Avada theme, so I need your plugin to work with it, or I will have to move to another option for card payments.

    Thanks a lot.

    Thread Starter kaostc

    (@kaostc)

    It is quite strange, cause I got this error with any plugin deactivated but woocommerce and woocomerce-gateway-stripe, and Twenty Twenty-five as active theme.

    Thread Starter kaostc

    (@kaostc)

    Rolling back to previous version (6.7.0) does not help.

    Theme is Avada. Avada + basic avada plugins + woocommerce + woocommerce-gateway-stripe does not work

    Twenty Twenty-five + woocommerce + woocommerce-gateway-stripe does not work.

    This fallback combination throws this information:


    Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, first array member is not a valid class name or object in /var/www/clients/client31/web50/web/wp-includes/class-wp-hook.php:324 Stack trace: #0 /var/www/clients/client31/web50/web/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #1 /var/www/clients/client31/web50/web/wp-includes/plugin.php(517): WP_Hook->do_action() #2 /var/www/clients/client31/web50/web/wp-content/plugins/fusion-builder/shortcodes/woo-checkout-payment.php(233): do_action() #3 /var/www/clients/client31/web50/web/wp-content/plugins/fusion-builder/shortcodes/woo-checkout-payment.php(207): FusionTB_Woo_Checkout_Payment->get_woo_checkout_payment_content() #4 /var/www/clients/client31/web50/web/wp-includes/shortcodes.php(434): FusionTB_Woo_Checkout_Payment->render() #5 [internal function]: do_shortcode_tag() #6 /var/www/clients/client31/web50/web/wp-includes/shortcodes.php(273): preg_replace_callback() #7 /var/www/clients/client31/web50/web/wp-content/plugins/fusion-builder/inc/class-fusion-column-element.php(588): do_shortcode() #8 /var/www/clients/client31/web50/web/wp-includes/shortcodes.php(434): Fusion_Column_Element->render() #9 [internal function]: do_shortcode_tag() #10 /var/www/clients/client31/web50/web/wp-includes/shortcodes.php(273): preg_replace_callback() #11 /var/www/clients/client31/web50/web/wp-content/plugins/fusion-builder/inc/class-fusion-row-element.php(123): do_shortcode() #12 /var/www/clients/client31/web50/web/wp-includes/shortcodes.php(434): Fusion_Row_Element->render() #13 [internal function]: do_shortcode_tag() #14 /var/www/clients/client31/web50/web/wp-includes/shortcodes.php(273): preg_replace_callback() #15 /var/www/clients/client31/web50/web/wp-content/plugins/fusion-builder/shortcodes/fusion-container.php(1095): do_shortcode() #16 /var/www/clients/client31/web50/web/wp-includes/shortcodes.php(434): FusionSC_Container->render() #17 [internal function]: do_shortcode_tag() #18 /var/www/clients/client31/web50/web/wp-includes/shortcodes.php(273): preg_replace_callback() #19 /var/www/clients/client31/web50/web/wp-includes/class-wp-hook.php(324): do_shortcode() #20 /var/www/clients/client31/web50/web/wp-includes/plugin.php(205): WP_Hook->apply_filters() #21 /var/www/clients/client31/web50/web/wp-includes/blocks/post-content.php(50): apply_filters() #22 /var/www/clients/client31/web50/web/wp-includes/class-wp-block.php(586): render_block_core_post_content() #23 /var/www/clients/client31/web50/web/wp-includes/class-wp-block.php(566): WP_Block->render() #24 /var/www/clients/client31/web50/web/wp-includes/class-wp-block.php(566): WP_Block->render() #25 /var/www/clients/client31/web50/web/wp-includes/blocks.php(2359): WP_Block->render() #26 /var/www/clients/client31/web50/web/wp-includes/blocks.php(2431): render_block() #27 /var/www/clients/client31/web50/web/wp-includes/block-template.php(294): do_blocks() #28 /var/www/clients/client31/web50/web/wp-includes/template-canvas.php(12): get_the_block_template_html() #29 /var/www/clients/client31/web50/web/wp-includes/template-loader.php(106): include('...') #30 /var/www/clients/client31/web50/web/wp-blog-header.php(19): require_once('...') #31 /var/www/clients/client31/web50/web/index.php(17): require('...') #32 {main} thrown in /var/www/clients/client31/web50/web/wp-includes/class-wp-hook.php on line 324

    Hope this helps!

    Thread Starter kaostc

    (@kaostc)

    Thanks, crystal clear.

    I had already enabled autosharing for tribe-events before starting this post, sorry I didn’t mention this, and I think it has generated confusion.

    The option for auto-sharing appears in new tribe-events and also when the tribe-event is saved as a draft. It even just after you publish, when the edit screen reloads. It is published and the controls for manual sharing are there, with a “share now” button.

    But if you leave this screen and then edit the published posts again, the link called “edit” that shows controls for manual sharing is gone. And the strange thing is that it is there but it is hidden via css, so I can perform a manual sharing by editing css in inspector and removing “display:none;” property.

    I think that for any reason It behaves in this way, and this is unsupported because it is just not checked to work.

    Thanks.

    Thread Starter kaostc

    (@kaostc)

    A bit confused with your answer…

    If you’re looking for some code customisation to help you with that, you may want to look at this page and see if you can adjust the code there to allow re-sharing, too.

    Please note that further assistance with custom code would go beyond the scope of our support, though.

    I don’t want you to generate custom code for me at all, but are you suggesting that “maybe” there is a feature similar to “publicize” that handles manual sharing?

    Cause you are encouraging me to investigate on this… but you support of this plugins, and knowing if such feature exist or not and communicating it clearly should be in the scope of your support. And providing reference on the available features that can be added to custom post should be also.

    So, I would be pleased if you clarify if such feature exist or not, or further than this, if you provide reference about what features Jetpack social provides that can be used by custom post types.

    Thanks a lot.

    Thread Starter kaostc

    (@kaostc)

    Thanks a lot for your help.

    I found that the problem was related with fusion-builder, a plugin bundled with Avada theme.

    I found a patch that solves this very situation.

    So everything is ok now. Thanks a lot.

    Thread Starter kaostc

    (@kaostc)

    I am trying to set up a test site to do what you suggest. Meanwhile I mark this ticket as resolved, and will open another one if I need to.

    Thanks.

    Thread Starter kaostc

    (@kaostc)

    I have tried to schedule a post again, without success (post was published in the site but not to social networks). This time Wordfence was in learning mode, which didn’t block anything.

    Wordfence stills in learning mode, can you reach now xmlrpc.php? Thanks.

    Thread Starter kaostc

    (@kaostc)

    Sorry about delay.

    The website is https://www.isf.es, and for the moment you cannot see any post not published, cause I have manually published those that has not been automatically.

    I am trying to share to Facebook, Threads, Instagram and Linkedin.

    I am using auto-sharing feature. It works perfectly if I manually publish the post with “Share while publish” enabled. It doesn’t if I schedule the post with “Share while publish” enabled. The behaviour I expect in this situation is that when the post change it status from Scheduled to Published on scheduled date, it is shared on select social networks. Please tell me if I am wrong.

    At the moment I have one scheduled post for tomorrow, and another for the day after tomorrow. If it goes as usual, they will be published but not shared on selected social networks.

    Thanks for your help.

    Thread Starter kaostc

    (@kaostc)

    I want that the header font in the frontend doesn’t affect to the post title in the backend. I want the backend to use the same font for post title, whatever font is used in frontend for headers.

    I am using Divi, but it also happens in twenty twenty-five.

    Thread Starter kaostc

    (@kaostc)

    Any help on this, please?

    Thanks a lot.

    Thread Starter kaostc

    (@kaostc)

    Found the way, works like a charm. I was setting the main content selector wrongly.