samwebdev

The bug is related to XML parse; xml downloads correctly when Stream Reader is enabled.

Do you plan for a fix for XMLReader? (XMLReader is much faster, but has a bug that sometimes prevents certain records from being imported with import files that contain special cases.)

Replicate:

https://sore-pony.w5.wpsandbox.pro/wp-admin/admin.php?page=pmxi-admin-import&action=index

Sample file:
https://cdn-09.anonfile.com/91cabah8o4/3b082bd4-1583942665/update1.xml

Sorry this is for product slider plugin:

https://www.ads-software.com/support/topic/compatibility-issue-elastic-press-elasticsearch-2/

Sure thing!

Cheers

• This reply was modified 4 years, 10 months ago by samwebdev.

Fuzzyurl is enabled, and is working with a single *, such as products/*/ where it does disable plugins for

products/tesla-car
products/macbook-pro

etc, nothing worked for /categories/categorya/categoryb/categoryc etc.

ended up using regex with a must use plugin.

if you get a chance, please implement regex solution in addition to *.

regards

It looks like Digits plugin is causing issue with the login.

closing ticket.

Bug is related to

https://www.ads-software.com/plugins/wp-mail-logging/

plugin.

Closing the ticket.

Hello Andreas,

Its 4.6.3, sorry for the typo.

* The issue is with all user accounts login
* There is a custom url assigned and issue seems to be for all translations
* Even with the ‘error’ text printed as the notice, the user is actually logged in, and they can go to their account.

4.6.2.1 doesn’t seem to have this issue.

Please let me know if you need any assistance in debugging the problem.

Hello,

The issue seems to be with the woocommerce-multilingual plugin v4.3

https://www.ads-software.com/plugins/woocommerce-multilingual/

Closing the ticket.

Regards

Hello Eva,

Did you get a chance to add/test this logic?

Would like to hear your take on this; it seems to work for us.

We just added/tested for google_shopping hence line 702; it could also be added for all, such as

for Yandex around line 707

if ( ($header == “true”) AND ($feed_config[‘nr_products_processed’] == 0) || !file_exists( $file ) ) {

if ($feed_config[‘name’] == “Yandex”) {

etc as needed.

Regards,

Sam

Hello Eva,

It looks like every project/product update/refresh needs to be flushed.

It might be better to add the flush to constructor (if any); if not these functions seem to require a cache flush:

function woosea_project_delete(){
function woosea_project_processing_status(){
function woosea_project_copy(){
function woosea_project_refresh(){
function woosea_project_status() {
function woosea_update_project_history($project_hash){
function woosea_create_all_feeds(){
function woosea_nr_products($project_hash, $nr_products){
function woosea_last_updated($project_hash){
function woosea_continue_batch($project_hash){

I will keep testing it with

function woosea_continue_batch($project_hash){
// Flush caching
wp_cache_flush();

..

for multiple exports with more than 25K products, and update it here.

If you can please also test it on your side (with Redis and/or any other object cache installed).

Changing the status of the ticket to unresolved in the mean time.

Regards,

Sam

Hello Eva,

Thanks just downloaded the new version.

One question though:

If you implement cache flush after the feed is requested, you may get the old data from database:

$feed_config = get_option( 'cron_projects' );
 $nr_projects = count ($feed_config);
	
 // Flush caching
 wp_cache_flush();

Could you move the

// Flush caching
wp_cache_flush();

lines right after the functions, line 2645 and 2491 respectively:

	public function woosea_project_update($project_hash, $offset_step_size){
		// Flush caching
		wp_cache_flush();

		$feed_config = get_option( 'cron_projects' );
		$nr_projects = count ($feed_config);

and

function woosea_continue_batch($project_hash){
	// Flush caching
	wp_cache_flush();

    $batch_project = "batch_project_".$project_hash;
	$val = get_option( $batch_project );

Thanks

Hello Eva,

In order to update the processing, its best to add these to 2 more lines:

woocommerce-sea.php

function woosea_continue_batch($project_hash){
wp_cache_flush();

around line 2644

class-get-products.php

public function woosea_project_update($project_hash, $offset_step_size){
wp_cache_flush();

around line line 2493

Thanks

Hello Eva,

Found out the issue, its not related to object cache.

There seems to be a logic missing.

Will open a new topic for the fix.

Edit: https://www.ads-software.com/support/topic/bug-fix-restarting-a-deleted-feed/

Regards

• This reply was modified 5 years, 9 months ago by samwebdev.

Hello Eva,

It works, thanks.

Please also work on the cache group feature, it should solve the cache issue for all.

Thanks,

Sam