Where is the change? I need to reimplement away from the dev site.
Festive wishes,
R
RR123
Participant
December 19, 2016 at 12:51
Sure thing – details in the private bit.
You can see the raw URL with the lack of necessary parameters in the cart, checkout and completed order pages. So I guess something didn’t ‘take’ across the board.
Many thanks!
R.
Please, contact administrator for this information.
RR123
Participant
December 19, 2016 at 12:47
login in private!
Please, contact administrator for this information.
RR123
Participant
December 19, 2016 at 12:46
Hello there
Logon details coming shortly!
1) Yes the plugin does work with the Storefront theme. I guess it needs to be installed in Xstore as per the minimal guide from Woo. It’s a question of where to put the php, child theme, etc?…
2) The problem with the linked product crossell was a core Woo problem. It does not show hidden items. It has to be viewable in the catalogue. Not your problem!
Thanks again!
R.
Please, contact administrator for this information.
RR123
Participant
December 19, 2016 at 12:44
Hi there,
Please look at the product URL I share in the private area. If you jump between stages in the component navigation, the JS will jump from component to component and back to the configuration as if the fixed menu is not there. So you keep having to scroll up a little each time.
I am very sure that I have seen other occasions when this happens, but did not keep a track. I guess there must some kind WP markup for the top of a page? surely this is true, otherwise other fixed header menus, like on mobile, would also suffer from this.
Thanks again!
R
Please, contact administrator for this information.
RR123
Participant
December 15, 2016 at 13:19
FYI Just tried the Linked Product cart crossell (standard woo feature) with Cart Addons disabled, but nothing showed at all – the linked products to crossell were ignored.
The cart item URL still just goes back to the basic product link, without the full parameter set.
This fix ‘super definitely’ made the update? Perhaps the temp fix for Deon is in place on his, so he wouldn’t see if the update didn’t carry the fix.
Many thanks again,
R
RR123
Participant
December 15, 2016 at 12:13
BTW I added the short code [display-addons length=5 mode=loop] to above the checkout shortcode on the checkout page, but it was a mess of filter and sort buttons and the addons themselves were not there.
Many thanks,
R
RR123
Participant
December 11, 2016 at 17:51
Works nicely for me, with a huge speed boost too to be honest
RR123
Participant
December 11, 2016 at 12:46
It could be my fault and it is somewhere, but I can never find this version history link and keep having to refer back to this message. Googling it doesn’t even bring it up easily. Could you add a link to the support docs?
Many thanks,
R
RR123
Participant
December 11, 2016 at 12:27
Sorry, crazy busy. I will come back to you about this!
RR123
Participant
December 11, 2016 at 12:26
Fantastic Olga – thanks!
RR123
Participant
December 2, 2016 at 18:36
Fabulous Olga – thank you!
RR123
Participant
December 1, 2016 at 17:43
Thanks guys. Details in private box!
Please, contact administrator for this information.
RR123
Participant
December 1, 2016 at 17:32
All is well. This is not your problem. I was looking at dev and production sites at the same time to test. But the dev site with storefront had a working coupon and the coupon on the production site was not showing for some unknown reason. It would show in the production “My Account” list of coupons but be usable… I noticed this when adding a new coupon on the production just now.
Clearly NOT a theme issue!
RR123
Participant
December 1, 2016 at 17:32
fabulous.
thank you olga
RR123
Participant
December 1, 2016 at 17:32
complete muckup – sorry. that reply was for the other thread. This order comment issue is still an issue…. i will come back with login again….
RR123
Participant
November 30, 2016 at 18:02
Hi again, did this make the last update?
RR123
Participant
November 30, 2016 at 17:09
Thanks Olga. Will do.
R
RR123
Participant
November 30, 2016 at 16:40
Hi there,
Understood, but confused… I didn’t realise you use a different lightbox.
What is the difference?
RR123
Participant
November 30, 2016 at 12:31
I forgot to ask, will this fix be in future updates?
I don’t want duplicate cpu clock cycle usage when it does.
thanks again
RR123
Participant
November 30, 2016 at 12:23
Wonderful Serg – thank you. I didn’t have a chance to reply yesterday.
Best wishes,
R
RR123
Participant
November 28, 2016 at 18:07
Hello,
I have just added sftp details to the private content
Please, contact administrator for this information.
RR123
Participant
November 28, 2016 at 17:15
Hi there,
I know that class was there – that’s why I was highlighting it to you. That way you could find the correct element efficiently and see that the lightbox does not work despite the correct markup i.e. the class and pretty attribute being there correctly.
In short and to recap, it works when you move to storefront………….
This is feeling a little circular today………
RR123
Participant
November 28, 2016 at 15:34
Hello,
Those console messages are not the issue, for a few of reasons I can be sure of.
The error path shows that these are messages from one of the hosting company’s ‘must use’ adminbar plugins. They are not of particular consequence, but more importantly this means that there are no console errors of any kind when not a user is not logged into an admin account or any account. There are no JS errors at all. But the light box problems still exists for composites and bundles.
The other point is that lightbox is working properly for the main product image you see at the top left (even with the console messages you highlighted). Just disable the ‘cursor’ and ‘pointer event’ CSS in firebug/dev tools for that image and you will see the lightbox work nicely.
I hope that helps.
R.
RR123
Participant
November 28, 2016 at 14:26
No idea about widgets – I never had to time to investigate totally. The change was dramatic enough to need to revert to the backup
RR123
Participant
November 28, 2016 at 14:06
Hello,
I touched nothing other than the update button in the screenshot, as I have done in the past with success on other upgrade versions. No theme folder was changed. I was running a child theme of xstore, that remained set in place when I checked after the upgrade issue.
I had to revert to a previous backup to be able to get my work done, but I do remember that colours and red Xstore imagery suddenly appeared across the frontend of the template immediately after that upgrade button click. So presumably theme options had been wiped…
R.
RR123
Participant
November 28, 2016 at 11:24
Examples in private details
Please, contact administrator for this information.
RR123
Participant
November 28, 2016 at 11:14
Direct URLs that show problem on the way too…. 2secs….
RR123
Participant
November 28, 2016 at 11:12
Details in the private info. Please can you let me know what you do to sort it. The details are for a dev staging area and I will need to implement on the production.
Thank you.
Please, contact administrator for this information.
