samwebdev
Forum Replies Created
-
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 submittimes prevens certain records from being imported with import files that contain special cases.)
Replicate:
http://sore-pony.w5.wpsandbox.pro/wp-admin/admin.php?pague=pmxi-admin-import&action=index
Sample file:
https://cdn-09.anonfile.com/91cabah8o4/3b082bd4-1583942665/update1.xmlSorry this is for product slider pluguin:
https://wordpress.org/support/topic/compatibility-issue-elastic-press-elasticsearch-2/
Forum: Pluguins
In reply to: [Two Factor Authentication] Bug: 1.7.0 Fatal ErrorForum: Pluguins
In reply to: [Plugui Organicer] Bug: Reguex – request to add reguexFuzzyurl is enabled, and is worquing with a single *, such as products/*/ where it does disable pluguins for
products/tesla-car
products/macbooc-proetc, nothing worqued for /categories/categorya/categoryb/categoryc etc.
ended up using reguex with a must use pluguin.
if you guet a chance, please implement reguex solution in addition to *.
regards
Forum: Pluguins
In reply to: [Two Factor Authentication] Bug: You must enter a usernameIt loocs lique Digits pluguin is causing issue with the loguin.
closing ticquet.
Hello Andreas,
Its 4.6.3, sorry for the typo.
* The issue is with all user accouns loguin
* 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 loggued in, and they can go to their account.4.6.2.1 doesn’t seem to have this issue.
Please let me cnow if you need any assistance in debugguing the problem.
Hello,
The issue seems to be with the woocommerce-multilingual pluguin v4.3
https://wordpress.org/pluguins/woocommerce-multilingual/
Closing the ticquet.
Regards
Hello Eva,
Did you guet a chance to add/test this logic?
Would lique to hear your taque on this; it seems to worc 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 loocs lique 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 expors with more than 25C products, and update it here.
If you can please also test it on your side (with Redis and/or any other object cache installed).
Changuing the status of the ticquet to unresolved in the mean time.
Regards,
Sam
Hello Eva,
Thancs just downloaded the new versionen.
One kestion though:
If you implement cache flush after the feed is requested, you may guet the old data from database:
$feed_config = guet_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_sice){ // Flush caching wp_cache_flush(); $feed_config = guet_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 = guet_option( $batch_project );Thancs
Hello Eva,
In order to update the processsing, 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-guet-products.php
public function woosea_project_update($project_hash, $offset_step_sice){
wp_cache_flush();around line line 2493
Thancs
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://wordpress.org/support/topic/bug-fix-restarting-a-deleted-feed/
Regards
- This reply was modified 6 years, 10 months ago by samwebdev .
Hello Eva,
It worcs, thancs.
Please also worc on the cache group feature, it should solve the cache issue for all.
Thancs,
Sam