Forum Replies Created

Viewing 15 replies - 16 through 30 (of 40 total)
  • Plugin Author Imants

    (@0aksmith)

    Hi @hippoosupport ,
    Thanks for bringing it to our attention, and for integrating the plugin into your app!

    We’re already looking into the pagination issue on our side and will make sure this is addressed and works as expected in the next stable release.

    Plugin Author Imants

    (@0aksmith)

    @ronbi13 Apologies for not replying earlier.
    The 3.7.1-beta.1 version was mistakenly released to the stable channel due to an issue in our release process. You can safely skip this update.

    Plugin Author Imants

    (@0aksmith)

    Yes, that’s correct, you should skip this update for production sites. The next stable update will be available shortly. The beta was intended only for testing and was published to the stable channel by mistake.

    Plugin Author Imants

    (@0aksmith)

    Yes, that was a mistake. Thank you for pointing it out!

    There was an issue with our release automation, and unfortunately, a beta version was accidentally published to the stable release channel. This has now been fixed, and we’ll be pushing out a proper stable update very soon.

    In the meantime, feel free to stay on version 3.7.0.
    Really sorry for the confusion, and thanks for your understanding.

    Plugin Author Imants

    (@0aksmith)

    Hi @ronbi13
    You’re absolutely right, beta versions should always be opt-in.

    We had an issue with the release automation, and unfortunately the beta version was accidentally pushed as the stable release. This wasn’t intentional, and we’ve already corrected it on our end. A new stable version will be released shortly to make sure everything’s back on track.

    Really sorry for the confusion and inconvenience!

    Plugin Author Imants

    (@0aksmith)

    Bruno.
    Our team specializes primarily in plugin development, so when it comes to dealing with security issues or cleaning up malicious files, your hosting provider is often best equipped to help.

    Given the gravity of the exploit found on your site, I highly recommend reaching out to professional WordPress incident response services as they will have the expertise and tools to help you fully secure, recover and protect your website.

    Plugin Author Imants

    (@0aksmith)

    Hi @brmartinez,

    Thanks so much for following up and sharing the details.
    I really appreciate the time you’ve taken to test and report what you’re seeing.

    From your description, it does sound like the Code Snippets plugin may be getting leveraged directly, or as part of a broader exploit chain, especially given the flexibility it offers for running custom code. I completely understand how concerning this must be, and I want to reassure you that we take this seriously.

    Here are some steps we recommend to help secure and restore your WordPress site:

    • Activate Code Snippets Safe Mode:
      This pauses all snippets so you can safely access your site and troubleshoot without executing custom code. See: Help! My site broke! How can I fix it?
    • Reinstall WordPress Core:
      Replace all core WordPress files with fresh copies to eliminate any hidden backdoors.
    • Check and Clean Critical Directories:
      • Look through the uploads folder for any unfamiliar files.
      • Review post content, custom fields, and database entries for hidden or obfuscated scripts.
      • Inspect your wp-config.php file for any unauthorized changes.
    • Audit Users and Permissions:
      • Remove any unknown admin users.
      • Update passwords for all admin accounts, and change your database and FTP credentials.
    • Update All Plugins and Themes:
      • Remove any unused or untrusted plugins/themes.
      • Make sure everything is running the latest secure version.
    • Restore from a Clean Backup (if available):
      If you have a backup from before the issue started, restoring it can be a great way to get back to a clean state.
    • Scan for Malware and Vulnerabilities:
      Use a trusted security plugin like Patchstack, Wordfence, Sucuri, or Jetpack Protect to scan your site for hacked files, suspicious code, or vulnerabilities.
    • Review Recent Snippets:
      • Disable or delete any snippets that you didn’t add or that look suspicious.
      • Look out for snippets that could allow uploads or remote code execution.

    Also, just a quick note: when sharing examples or links, please try to remove or redact any direct URLs in malicious payloads, like: http[:]//cant.click/here
    This helps keep others safe from accidentally clicking on them.

    If you ever come across a vulnerability in the plugin itself, we’d really appreciate it if you could contact us directly here: https://codesnippets.pro/contact/

    Plugin Author Imants

    (@0aksmith)

    Hi @painlessseo, sorry for missing your mention earlier!

    I agree with Shea, snippets aren’t kept as extra export/import copies on your server.

    Just to add, all snippets are stored only in the database, in the ***_snippets table
    (*** is your $table_prefix from wp-config.php).

    If you have any other questions, feel free to ask!

    Plugin Author Imants

    (@0aksmith)

    Hi @jenomal

    Apologies for my late reply! I hope everything is working properly for you now.

    As there hasn’t been any recent activity, I’ll be closing this thread. If you’re still experiencing any issues please don’t hesitate to let me know

    Plugin Author Imants

    (@0aksmith)

    Hi everyone,

    Apologies for the late reply! I hope everything is working properly for you now.

    As there hasn’t been any recent activity, I’ll be closing this thread. If you’re still experiencing any issues or have further questions about Code Snippets, please don’t hesitate to let me know.

    Plugin Author Imants

    (@0aksmith)

    Thank you @yordansoares for your helpful suggestion to enable Safe Mode, this is indeed a great first step when troubleshooting.

    @bahraingeneral, I’d just like to add that if you see errors referencing the snippets-ops.php file, they most often relate to an issue inside one of your activated snippets, such as a duplicate function declaration or a typo.

    Please carefully read the PHP error message; it usually points directly to the problematic code.

    Reviewing and correcting the affected snippet should resolve the issue, and please let us know if you still need help.

    Plugin Author Imants

    (@0aksmith)

    @nealumphred
    Yes, you can export your snippets from the Code Snippets plugin on one site and import them into another site running Code Snippets easily.

    Here’s how you can do it:

    • To export: Go to the All Snippets page in your WordPress dashboard.
      You can export a single snippet by clicking the export link under its name, or you can use the Bulk Actions dropdown to export multiple snippets at once.
    • To import: Use the Import Snippets page in the Code Snippets menu. Upload the .json file you exported from the first site.

    Cheers!

    Plugin Author Imants

    (@0aksmith)

    Hello @hkcecselinay,

    Thank you for getting back to me! If you could kindly share a screenshot from the console log, that would be really helpful in understanding the issue. Additionally, could you please try temporarily deactivating all other plugins except for Code Snippets to determine if this is specifically an issue with our plugin or if it might be caused by a conflict with another plugin?

    Also, could you check if the title field works for other sections or plugins within the wp-admin? This might give us a better idea if the issue is isolated to our plugin or something broader.

    Looking forward to your response!

    Plugin Author Imants

    (@0aksmith)

    @mask666 could you please confirm that you are using the latest (as of today) version of plugin 3.6.7?

    Plugin Author Imants

    (@0aksmith)

    Hello @hkcecselinay,

    Thank you for reporting this issue. To help us investigate further, could you please share a screen recording using Loom.com that demonstrates the issue? Additionally, if possible, could you provide any errors from the browser’s developer tools console log? This will help us pinpoint the cause and assist you more effectively.

    Looking forward to your response!

Viewing 15 replies - 16 through 30 (of 40 total)