Moving from another plugin

@joyryde Inndesign shared a link, but we do not market or promote plugins.

Plugins by default use different database field naming conventions, to distinguish one plugin from another, otherwise, the combined installations would generate conflicts. There are no instant solutions to assure any transition from one plugin to another within the same genre.

Please refer to “How do I export the Product Code field from WooCommerce?” from the description page. Use this method to both export and import the data. An experienced database developer would be able to do this in a matter of minutes. The two fields to import to is “_product_code” (for simple items) and “_product_code_variant” (for variable items). The “WooCommerce UPC, EAN, and ISBN” plugin should have database tables, one for each of these two.

As you can imagine, we cannot provide database support for users. We are not paid a penny for developing or maintaining these plugin. A URL link from the plugin installation requests donations to a not-for-profit for the needy is the only compensation.

Thanks!

@joyryde Sorry for the delay. This has been resolved with version 1.2.0 updated to the repository. Once the plugin is updated, it will request a database update, which will merge the tables into one meta table called “_product_code”. Any search plugin will need this entry revised and reindexed, as detailed on the description page. From the setting panel, there is now an import/export option using the JSON data-interchange format. Please leave a raving 5-star review where this was costs I took on myself.

Plugin installation failed.

Upon activation the website had the following errors at the top of the page:

oyryde/djdeals.com/wp-content/plugins/product-code-for-woocommerce/modules/search/pwfa-export-support.php): failed to open stream: No such file or directory in /wp-content/plugins/product-code-for-woocommerce/product-code-for-woocommerce.php on line 49

Warning: include(/wp-content/plugins/product-code-for-woocommerce/modules/search/pwfa-export-support.php): failed to open stream: No such file or directory in /wp-content/plugins/product-code-for-woocommerce/product-code-for-woocommerce.php on line 49

Warning: include(): Failed opening ‘/wp-content/plugins/product-code-for-woocommerce/modules/search/pwfa-export-support.php’ for inclusion (include_path=’.:/opt/cpanel/ea-php73/root/usr/share/pear’) in /wp-content/plugins/product-code-for-woocommerce/product-code-for-woocommerce.php on line 49

Warning: Cannot modify header information – headers already sent by (output started at /wp-content/plugins/product-code-for-woocommerce/product-code-for-woocommerce.php:49) in /wp-includes/functions.php on line 6270

Warning: Cannot modify header information – headers already sent by (output started at /wp-content/plugins/product-code-for-woocommerce/product-code-for-woocommerce.php:49) in /wp-includes/functions.php on line 6270

Warning: Cannot modify header information – headers already sent by (output started at /wp-content/plugins/product-code-for-woocommerce/product-code-for-woocommerce.php:49) in /wp-admin/includes/misc.php on line 1310

Warning: Cannot modify header information – headers already sent by (output started at /wp-content/plugins/product-code-for-woocommerce/product-code-for-woocommerce.php:49) in /wp-admin/admin-header.php on line 9

__________________________________________________________________________

There was also a big red warning across the top of the page stating:

The plugin generated 1060 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

How strange. A couple of users are noting this issue, others are not. We certainly want to apologize for this problem.

There is an error in the download repository looking for the file /modules/search/pwfa-export-support.php which does not exist under that folder. The correct file is located at /modules/export/pcfw-export-support.php.

I have reloaded the same build which is working fine on our staging sites, which should fix the repository file stream with www.ads-software.com. There is nothing wrong with the plugin, it is the download stream that has corrupted the location of the file.

Please fully delete and replace it with version 1.2.1 and let us know right away if there are further issues. There should not be, but there shouldn’t have been with the previous version either.

Installed Version 1.2.1, same errors, uninstalled and deleted.

I sent an urgent message to the developer, to look into providing a new build immediately. We have it running without error on the staging site and a working client site, therefore it is a baffling issue.

Could you try it again, delete and install and see what happens? I just copied pcfw-export-support.php to the /search folder. It doesn’t below there, but it will work there. For some reason, the repository is not correcting the file location.

Thanks.

@joyryde Could you kindly try it again, delete and install and see what happens? The developer provided new files. I tried the plugin on a fresh WooCommerce build and an older one and no errors appeared. So sorry for the inconvenience.

Hello @joyryde. Unfortunately, my new developer and I are not on the same page regarding certain details on this plugin. We have uploaded a completely new compiled plugin as version 1.2.2. I checked the files carefully and all the internal URI’s are correct.

The plugin functions fine despite the above errors. What is happening is the export module wasn’t able to find it’s function file, throwing URI errors. Your current WordPress configuration is set up to show all errors, even those not fatal.

I would configure your wp-config.php file with this code inserted BEFORE /* That’s all, stop editing! Happy blogging. */. It forces WordPress to log all errors, notices, and warnings to a file called debug.log in the wp-content directory. It will also hide the errors so they do not interrupt page generation.

// Enable WP_DEBUG mode
define(‘WP_DEBUG’, true);

// Enable Debug logging to the /wp-content/debug.log file
define(‘WP_DEBUG_LOG’, true);

// Disable display of errors and warnings
define(‘WP_DEBUG_DISPLAY’, false);
@ini_set(‘display_errors’,0);

// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define(‘SCRIPT_DEBUG’, true);

Hope this works!