Forum Replies Created

Viewing 15 replies - 91 through 105 (of 1,297 total)
  • csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    The tax calculations are done on the WooCommerce side of things. While it uses the Jetpack connection to WordPress.com, the functionality is on WooCommerce’s side.

    Jetpack Support doesn’t have any insight or knowledge into how those tax rates are calculated, if you’re seeing a bug, or if there’s another setting you need to get this to work. We can help with the general connection from your store through Jetpack – but this is not something we can help with. But someone from Woo Support can, which is why I requested this be moved to Woo’s support forum.

    Edit: It looks like was moved already.

    • This reply was modified 5 years, 8 months ago by csonnek.
    csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @jordanwebdev hi there! This is more of an issue with WooCommerce than with the Jetpack tools. I’ve requested that the WordPress.org moderators move this to the WooCommerce forum for help.

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @brulosopher I see the same behavior on the WordPress.com dashboard, which would indicate your theme or another plugin is not compatible with the WordPress.com editor.

    Let’s rule out a plugin conflict first. Disable all other plugins and keep Jetpack active. Then disconnect and reconnect Jetpack to your WordPress.com account and see if you can edit posts there again.

    I did notice there’s a Tiny MCE plugin active, which is only for the Classic editor, so that might be the culprit, but I’d like to disable all the plugins first.

    If things start working again, start turning your plugins back on one by one until you see the same problem again. That will indicate the plugin that is incompatible with the WordPress.com editor. This might be a good chance to audit the plugins you have activated and remove any you’re not using.

    Let us know how that goes!

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @laurencet thanks for that!

    While your site is publicly accessible, we cannot access your site’s XML-RPC file:
    http://www.wharfedalebka.org.uk/xmlrpc.php

    This file is used by Jetpack and other plugins and apps to connect to your site. It must return the following message:
    XML-RPC server accepts POST requests only.

    You can see a working example here:
    https://jetpack.com/xmlrpc.php

    Since your site returns a 403 Forbidden error for this page, I would recommend that you check the following:

    1. Do you use any security plugins that may block access to this file? If so, could you try to disable them? You might also want to check your site’s .htaccess file for any rules that might be blocking access to the xmlrpc.php file.
    2. Does your hosting provider block access to this file? If you don’t find any plugin that may block access to the file on your site, I would recommend that you get in touch with your host.

    Let us know if you still have trouble after restoring access to that file and we’ll be happy to help.

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @jontwerp can you let us know the following?

    1. The URL of your WordPress.com site where your followers were (example.wordpress.com)
    2. The URL of your site that you moved them to. You do need to have an active Jetpack connection in order to do this.

    The site you gave us – grofvankoren.com – is a WordPress.com site so we need more information before we can dig into this further.

    Thanks!

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @marcobutz thanks for getting in touch!

    While your site is publicly accessible, we cannot access your site’s XML-RPC file:
    https://www.artedimare.de/xmlrpc.php

    This file is used by Jetpack and other plugins and apps to connect to your site. It must return the following message:
    XML-RPC server accepts POST requests only.

    You can see a working example here:
    https://jetpack.com/xmlrpc.php

    Since your site returns a 405 error for this page, I would recommend that you check the following:

    1. Can you see the /xmlrpc.php file at the root of your WordPress installation when accessing your site via FTP? If you don’t, then please try re-installing WordPress. You can do this by going to the Dashboard -> Upgrades page, then click the “Reinstall WordPress” button.
    2. Do you use any security plugins that may block access to this file? If so, could you try to disable them? You might also want to check your site’s .htaccess file for any rules that might be blocking access to the xmlrpc.php file.
    3. Does your hosting provider block access to this file? If you don’t find any plugin that may block access to the file on your site, I would recommend that you get in touch with your host.

    Let us know if you still have trouble after restoring that file and I’ll be happy to help.

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @kmiles2505 we’re the same support staff here in the forums that are staffing our email.

    We also don’t log into your site and do these things for you, so regardless of whether or not we help you here or via email, you will need to do this yourself.

    Are you not able to copy and paste the code my colleague Jeremy posted above?

    If you continue to have trouble or aren’t sure how to add this, I highly recommend you contact your hosting provider for help here. Since they’re hosting your site’s files, they also have access to those files and are the best ones to help you get this code added to your site. It looks like your site is hosted with Bluehost – you can reach them directly here:

    https://www.bluehost.com/contact

    It looks like we also replied to your email (ref 3538179) yesterday. Please keep your correspondence to that email so we can keep everything together. But, before you reply again to that email, contact Bluehost and get their help adding that code.

    Please direct any other questions to that email. Thanks!

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    Thank you for taking a look into it. I have just checked, and even tried to reconnect, but it appears that the data is still not there.

    Thanks for getting back in touch! It looks like what my colleague merged in was stats data for an ID that only had stats from Sept 2015 to Oct 2015.

    I dug into this further and it looks like the data from 2015 to 2020 was tied to an ID using an IP address rather than your domain name. I merged that data in and it should show up right away – no need to wait or disconnect/reconnect things.

    Let us know if you see the data you expect now!

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @eriol8 – thanks for reaching out!

    Hi all, I recently moved over from a WordPress.com hosted Business Plan to a self-hosted WordPress.org blog. Ever since moving using the All-in-One WP Migration tool, I’ve been having issue with getting the Jetpack to work properly

    It looks like AIO copied the site blog token information from the WordPress.com Business site which is why you’re seeing issues.

    Jetpack saves a blog ID and a token (think username and password) in the database when you first connect that is unique to specific URL. This same blog ID and token is used on WordPress.com sites.

    Since you used AIO to clone a live, active, connected site to a new site, then the new site is trying to interact with WordPress.com using the original WordPress.com site’s information.

    To fix this, disconnect and delete Jetpack on your new self-hosted site. Then reinstall and reconnect it to your WordPress.com user account. That should take care of it. You can respond to this thread and we can check on our end after you do that to make sure your new self-hosted site generated its own unique blog ID and token.

    Let us know if you have any questions. Otherwise, we’ll wait to hear back from you!

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    You’re welcome! Let us know if we can help in the future. πŸ™‚

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @abicatian – I can, but I can’t reset it to a specific date in the past – when I flip the switch, they reset from that point on. This is also a back and forth process, which involves the following:

    1. Disconnect Jetpack on your end.
    2. We’ll start the process to reset your prior stats data.
    3. We’ll let you know when that is done and you can reconnect Jetpack.

    Once the process has completed, your stats will be completely reset.

    Can you let me know what site you’re wanting to reset your stats? Once I have that information, I’ll be better able to help.

    If you want it to remain private, you can also contact us via this contact form and mention this thread.

    Thanks!

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    However, I have spotted a couple of possible issues (though not the end of the world) at the foot of the automated email as captured via snipboard (URL below)

    In testing, it doesn’t appear that all tags will be included in the email, so that appears to be the expected behavior. The category should have, though.

    Can you let me know what site you’re having this problem? Once I have that information, I’ll be better able to help.

    If you want it to remain private, you can also contact us via this contact form and mention this thread.

    Thanks!

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @adminlibreriaurano – Troubleshooting these things falls outside the scope of support we can provide in the forums. Since this isn’t a Jetpack problem – because we don’t ship our own jQuery in our plugin – this is more a general WordPress troubleshooting issue.

    I’d recommend reaching out to the WordPress community for guidance on how to resolve your jQuery conflict:

    https://wordpress.org/support/forum/how-to-and-troubleshooting

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @charlinehm thanks for the update! Happy to hear you were able to find what was causing the problem.

    Let us know if we can help with anything related to the Jetpack plugin in the future.

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer πŸš€

    @stefconnermusic – no apologies necessary! We’re glad you were able to sort out the problem πŸ™‚

    Let us know if we can help with anything related to the Jetpack plugin in the future.

Viewing 15 replies - 91 through 105 (of 1,297 total)