• Lots of people are saying there data is gone but it’s not entirely true. They change the name of the custom post type from from tshowcase to team_mf and did not make it backwards compatible. So the entries are still in your database but the custom post type is no longer being registered or accessed.

    Should be an easy fix for them.

Viewing 1 replies (of 1 total)
  • Plugin Author themepoints

    (@themepoints)

    Thank you for reaching out to us.

    This issue typically occurs during plugin updates—particularly automatic updates—due to a naming conflict between two different plugins that happen to use the same slug (team-showcase). When we initially released our plugin, the automatic update feature was not available. However, with its later introduction, the update system began relying on the plugin’s slug and folder name to identify updates.

    Unfortunately, because both plugins share the same slug, the update process may mistakenly overwrite one plugin with the other, even though they are developed by different authors and distributed through separate marketplaces.

    We would also like to clarify that we are not affiliated with the plugin available on CodeCanyon. Our plugin is entirely separate and unrelated to the CodeCanyon version. If you check your purchase records, you will find that your plugin was obtained from the CodeCanyon marketplace.

    We sincerely hope this explanation helps clarify the situation. If you now have a better understanding of the issue, we kindly ask you to consider updating your feedback. A positive review would mean a great deal to us and help support our continued development.

    Thank you once again for your time and understanding.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this review.