Comments,likes not working on localhost

Jetpack requires your site to be publicly accessible in order to connect with WordPress.com.
Since you work in a local environment, Jetpack automatically switched to the development mode, where you can use all Jetpack features that do not require a WordPress.com connection.

If you want to try Jetpack Comments or Likes, you will need to do so from a live site.

I hope this helps!

What is this for stupid thing ?
People need to tweak and style comments to adapt it to the rest of website.

Sorry, but from people behind WP core and Jetpack someone wouldnt expect “Microsoft” stupidity.

People need to tweak and style comments to adapt it to the rest of website.

To be clear, Jetpack and its comment module don’t affect the look of comments on your site; that’s entirely controlled by your theme, and can be tweaked and styled on a local installation. Jetpack Comments only replace the comment form, and this comment form cannot be customized from your WordPress installation.

If you’d like to play with the Jetpack modules that require a connection to WordPress.com, you could create a test site on a publicly accessible server.

OK. Maybe understandable for comments, iframe, bots, antispam and such.

What for other plugins. Put at least price on them, difficult to understand when something is done without reason. Or on Jetpack blog explain in detail why you do so.

Your debug line in wp-config.php never completely worked for me. Only when i remove almost all lines in jetpack data class PHP, or what is it called.

What for other plugins. Put at least price on them, difficult to understand when something is done without reason. Or on Jetpack blog explain in detail why you do so.

I’m not sure what you’re referring to. All Jetpack modules are free. Could you give me more details?

Your debug line in wp-config.php never completely worked for me.

Could you give it another try, or use the jetpack_development_mode filter instead, as explained here:
https://jetpack.me/support/development-mode/

If you use the JETPACK_DEV_DEBUG constant, you’ll need to place it right before this line in the wp-config.php file of your local installation:

/* That's all, stop editing! Happy blogging. */

It should look like this:

https://i.wpne.ws/UFmy

Let me know if it helps.

Never mind, i highjacked topic anyway.
Just wanted to say Jetpack is complicated and confuse for a reason i cannot see.

What Infinite Scroll has to do with www.ads-software.com. I cannot activate it.

What Infinite Scroll has to do with www.ads-software.com. I cannot activate it.

Once you activate the development mode, you’ll be able to use the Infinite Scroll module, since it doesn’t require a connection to WordPress.com.

I tried all you said. OK, now when removing code from class.jetpack-data.php i see that my theme doesnt support Infinite Scroll.

With your advices out of 32 plugins i can activate 12 plugins.
Removing code from class.jetpack-data.php allows activating of 31 plugins.

Tell me just is that number 12 standard and normal behaviour ?

With your advices out of 32 plugins i can activate 12 plugins. Tell me just is that number 12 standard and normal behaviour ?

It’s actually 13 as of Jetpack 2.9. That’s the number of modules that do not require a connection to WordPress.com at the moment:

1. Carousel
2. Sharing
3. Gravatar Hovercards
4. Omnisearch
5. Contact Form
6. Widget Visibility
7. Custom CSS
8. Shortcode Embeds
9. Mobile Theme
10. Markdown
11. Beautiful Math
12. Extra Sidebar Widgets
13. Infinite Scroll

All the other modules rely on the WordPress.com infrastructure. You may be able to force activate them by making changes to the plugin files, but they won’t work properly.

If you have questions about a specific module, and wonder why it requires a WordPress.com connection, do not hesitate to ask, I’ll be happy to help.

Developing on xampp/localhost, When the contact form is viewed, the username and email of admin are filled in. The visitor should see blank fields here to fill in, yes?

If you require assistance then, as per the Forum Welcome, please post your own topic instead of tagging onto someone else’s topic.

I am now closing this 10 month old, resolved, topic as it references an older version of WordPress.