regisit

As Fibo has a hook when initiating a search, I added this to functions:

// Manage search - Relevanssi for admin, Fibo for frontend
add_filter( 'dgwt/wcas/helpers/is_search_query', 'motor_manage_search' );
function motor_manage_search( $query_object )
{
    // Remove Relevanssi hooks
    remove_filter( 'posts_search', 'relevanssi_light_posts_search');
    remove_filter( 'posts_search_orderby', 'relevanssi_light_posts_search_orderby');
    remove_filter( 'posts_request', 'relevanssi_light_posts_request');
}

Works a treat! Much faster search front and back now.

Excellent – thanks! I had just this minute opened the source code to look at the hooks being used to see if these could be deregistered.

My focus is on the product listings page so should be able to deregister them in general but not when on the admin listing pages.

Thanks Konrad. Can confirm the patch fixes it.

Great support! ??

Just one comment if I may. Looks a tiny bit untidy as all fields briefly appear stacked and full width before realigning into columns. If it were possible to fix that it would be good.

Seems to be an issue with CSS:

.acf-fields.acfe-column-wrapper>.acf-field.acf-field-acfe-column[data-columns=”2/12″] {
width: 16.66666%;
float: left; – missing
}

Plus acf-input.css line includes:
.acf-field {
margin: 15px 0;
clear: both; – destroys floats on each field!
}

Add float:left and remove clear:both and then it display in columns.

Ok, thanks for confirming. Perhaps a little key as to what the Pro icons mean would help avoid confusion.

However, cleared cache (browser, Rocket and Opcache) and still no columns. Also tried resaving field group, using another browser and incognito.

Any other ideas?

Ok, thanks. Will raise a ticket to have this hot-fixed.

Where are you at with releasing the full source code? As you’re aware, this is and always has been a requirement of both WordPress and OpenSource GPL in general. Last on this was 10 months ago where you agreed to comply with the non-compliance request from WordPress but still the source is not available or requestable.

If we had the full source code and not just part of it, we could fix this ourselves while we wait for a core fix.

@ezdoss Have emailed you again if you could check. Tks.

Done.

@ezdoss I have made contact through your contact form.

@ezdoss Are you able to publish what you have? Would be willing to assist with this and/or contribute cost-wise. Technical knowledge is not an issue. Thanks.

@ezdoss – any news on your custom development? I suspect a great many POS users have no need of cloud print functionality and just need to be able to print a traditional receipt. Disappointing to see that this has not been accommodated and we’re expected to pay a monthly fee just to print to a locally attached printer.

As the POS client-side source code has still not been released – which goes against everything OpenSource stands for as well as all the legal requirements for using OS code – how are you going about this?

Thanks

• This reply was modified 4 years, 2 months ago by regisit.

If this is business critical for you, we’d recommend evaluating other options now as a back-up plan to be safe,

Do you have any recommendations for alternative print solutions for your POS or are you advocating customers look for alternative POS solutions?

What about a simpler print solution not involving cloud print but just standard local (USB) or network attached (ethernet/wifi) printers? As I said in another post, in many (if not most) situations cloud print is not required. We simply need to be able to print to local printers. This should be a long-term solution, as well as Cloud Print if there’s still a need for it. Essentially that means people needing to print to other locations than the site they’re at.

That would also remove a potential source of failure. While the POS can still process orders if the internet is down, using GCP for all prints means receipts can only be printed when online. And then there’s the delay routing all receipts through GCP causes.

It’s probably telling that Google is shutting down their cloud print service, maybe because it’s not really a thing people need/use.

I’ve been speaking with POS hardware vendor and they have said GCP causes issues for standard POS operation. They believe it’s not possible to usual thermal receipt printers attached to cash draws when GCP is in the equation.

Maybe a daft question, but have you considered a solution that offers local printing? Or is there a solution already?

While using a Cloud Print service may be an essential requirement for some, for many it’s overkill as they need little more than the ability to print a traditional receipt on a local printer attached to their POS device.

Ok, thanks for the info. I can confirm:

1. 1hr background sync of product changes works fine.
– being able able to change the auto-sync frequency would be more flexible to accommodate different store needs.

2. Forcing sync of Groups works to update the add-on info.
– should really be happening as part auto-sync.

3. More flexible options for product tabs – shame!
– some POS installations would benefit from being able to create a screen of common products.

4. Customisation – ok no further mention of this!

As per response to pre-sales, where can we download a copy of the full source code? Not available on GitHub. Obviously the webpacked POS side JS is undecipherable.

Thanks

After some debugging of the API calls from the app I can see the issue with 1 & 2.

1. There doesn’t appear to be any scheduled background sync. Only regular activity is a heartbeat. How is the POS cache kept in sync if it doesn’t check for updates?

2. A full manual sync doesn’t fully sync Groups. I see a call to wc-pos/groups/ids which only returns a list of group Ids. There’s no call to wc-pos/groups which would update the cache with any changes to the content of add-on groups. Appears that only happens when the local cache is deleted.

As the POS frontend has been webpacked, that’s about as far as I can go as it’s impossible to trace what the browser side is doing (or not!).