Sure thing – I shall do.
To be honest, I didn’t notice the sidebar changing behaviour when this feature was activated. But perhaps there were not enough posts to make a long enough page for the sidebar to stick.
Sure thing – I shall do.
To be honest, I didn’t notice the sidebar changing behaviour when this feature was activated. But perhaps there were not enough posts to make a long enough page for the sidebar to stick.
Sure thing – details of the page with login in the private bit.
Thanks Olga
Hi there,
If I tick “Show buttons on” / “Posts” on /wp-admin/options-general.php?page=sharing I get your nice sharing buttons with the ugly ones added above them, which is right after the article:
They are ugly compared to yours, but they have some useful other social/msg’ing links that I need.
Thanks Olga. I’ll put this in place too
Wonderful – thanks Olga
R.
Hello Olga,
Thank you the file. I have put in the location and shall text when I have a moment.
BTW will this fix be implemented in later Xstore updates? I ask to make sure the fix is not erased by any future updates.
Many thanks Olga – that’s great (I just found it in my spam).
R.
Thank you Olga – that would help. I do appreciate your proactive resolution.
Is it just a case of installing the plugin normally? I am happy to do that myself (it would need to be on a diff test site than the host shared in the WC Social Login plugin thread).
Regards,
R
Hi ahumado/Olga,
Thanks for both your messages. I should add that I am a WP newbie (but not a tech newbie).
To take Qs in turn:
Thanks again,
R
Thanks Olga.
Richard
Thanks Olga. Admin login details are in the private content. You should go to “My Account” in WooC and then Account Details and at the bottom you can try to add a social account to see the error.
NB this server is on a diff domain to our main test site that is actually tied into FB, LI and other social API credentials. So you should still get errors from the social networks themselves if it were working. But it doesn’t get that far and dies with the same ‘local’ 500 error (like the main test site).
Sadly, I can’t give you FTP access because the way our setup works. Let me know if you need anything done there.
R.
Thanks – very helpful
Actually, it works fine in Incognito mode while on another install. So clearly something specific to main test install. I have a Maintenance Coming Soon mode thing installed on the main one as it is the live domain…. might be that.
Let’s assume it’s ok for now. Will keep you posted after launch if needed.
Thanks,
Richard
Hi,
Yes, even with these settings added. It does seem a little faster with those settings, but could be my imagination. But there are still errors (at bottom).
Your screenshot did have some hidden collapsed option sets, so I experimented. The first error you see below with ‘line 2525’ is with the Enable Lazy Load option ticked. When it is unticked, it is still the ‘line 46 error again’.
I am pasting some of your screenshot text to double check, as some characters might be ambiguous:
etTheme.loadInView();
jQuery('.filter-wrap .pagination-cubic').hide();
Thanks,
Richard
Oct 20 16:50:34 192.168.170.63 apache2[2281]: [u1066] [test.on.com] [82.40.180.13] [Thu Oct 20 16:50:34 2016] [error] [pid 2281] mod_proxy_fcgi.c(673): [client 192.168.144.252:40182] AH01071: Got error 'PHP message: PHP Notice: Undefined index: lazyload in /test-www/wp-content/plugins/sb-woocommerce-infinite-scroll/sb-woocommerce-infinite-scroll.php on line 46\nPHP message: PHP Notice: Undefined variable: context in /test-www/wp-content/plugins/subscriptio/subscriptio.php on line 2525\nPHP message: PHP Notice: Undefined variable: context in /test-www/wp-content/plugins/subscriptio/subscriptio.php on line 2525\n'
Oct 20 16:50:36 192.168.153.168 apache2[7256]: [u1066] [test.on.com] [82.40.180.13] [Thu Oct 20 16:50:36 2016] [error] [pid 7256] mod_proxy_fcgi.c(673): [client 192.168.144.252:36110] AH01071: Got error 'PHP message: PHP Notice: Undefined index: lazyload in /test-www/wp-content/plugins/sb-woocommerce-infinite-scroll/sb-woocommerce-infinite-scroll.php on line 46\n'
I might have fixed it with the below CSS…. not really tested this properly though but it seems to work like a failsafe mechanism.
It’s just a quick hack to fade in the element, which from what I can see never get’s a change anyway because the AJAX is faster. The AJAX seems to trigger way before this fadein is relevant and make the cart total properly visible when the AJAX is ready.
Again, it’s just a quick hack, I think…….
/* fadein cart widget total to get rid of server caching vs ajax problem */
.shopping-cart-widget .shop-text .amount{
-webkit-transition: opacity 20s 10s ease;
-moz-transition: opacity 20s 10s ease;
-ms-transition: opacity 20s 10s ease;
-o-transition: opacity 20s 10s ease;
transition: opacity 20s 10s ease;
}
the others, i meant
(edit not working for some reason)
Hi,
Just does work on a per product basis after all…
All well on this point!
Please do.
I am very disappointed indeed. Pricing tables were promised by the 18th October and today is the 20th. We purchased on the 4th and they promised them for within 10-14 days.
We were at pains to triple confirm with 8theme that this would happen before we bought Xstore, as they are that important for us.
We do like your support otherwise and there was that goodwill. I really hope you catch up with this ASAP as we feel like hostages now… plus there are the other posts with issues that also came up just in the past few days sadly.
Really needing action and practical reassurance,
Richard
Aha… I had puzzling over this same issue… I tried removing Facebook login credentials from the 8theme settings, but it didn’t fix it.
Was there a resolution?
Richard
Thanks Olga. Please do…
Hi Olga,
Thanks your your reply. This very sounds good, but I guess this could take unknown period of time for now which is scary for us having invested time already… Our biz is not far from prelaunch (days) and depends massively on these tables.
Is there a temporary hack or work around based on Legenda created code, for example, that comes to mind?
I should also add that the prob is not always there. I guess it will completely depend on what is being cached by the WP server and then in the browser in that particular moment.
I can be sure that it is definitely happening because 1) in one woocommerce guest session there was a £x total and 2) another woocommerce guest session running in incognito mode flashed up the other session’s £x total briefly before the AJAX showed the correct £y total.
My thinking if it helps:
I guess the CSS needs to make it display:none until the AJAX kicks in (easy enough to DIY here), but the important problem that stops us from this DIY fix is that the AJAX would need to make it display:visible right after updating the value…
Hi,
Just before we went ahead and bought Xstore they did say that feature will be out around now.
It is a nice theme and support has been very good so far, so it probably will be 🙂
Hope so, or we’ve got a big problem…(!).
Hi there,
I just saw another update…. did the pricing tables come through after all??????
Thanks,
Richard
Understood. Thanks Olga. Have a good weekend
Thanks Olga!
🙂
Many thanks Olga – makes sense. You are a star!
Which CSS would do the same for the wishlist in all scenarios? I just noticed that’s affected too and want to make sure I cover the correct classes…
Thank you!
(edited typos…)
I am just messing around with it and I see the alignment problem depends on the digits of how many things are in the cart. But the issue is always one of being too left….
Finally back at PC… pics in private link!