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.
Best Regards
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.
Best Regards