mrboats
Forum Replies Created
-
Having the text for a checkbox to be very long is not good UX/usability. Therefore it would be better if there was a separate text string with explanatory text so that the “label” for the checkbox can be kept very short and understandable. The text could be something like “By ordering this product I agree that my ….. For a full information on how your data will be processed….. jada jada jada”.
Yes, after terms and conditions would be a good placement! Also there should probably be an explanatory string that could be placed just before terms and conditions. If this string is set in admin (it could also be a translatable string in .po file), then it should be passed via _e() or __() to be translatable.
- This reply was modified 8 years, 3 months ago by mrboats.
Forum: Plugins
In reply to: [Open Graph and Twitter Card Tags] YITH Vendor page issuesThe plugin is this: https://yithemes.com/themes/plugins/yith-woocommerce-multi-vendor/.
I’m sorry but I do not understand your second answer? How do I use the fb_og_image filter in this case? I have set all options in the in this setting: https://www.dropbox.com/s/8iavnlsk6iynw7p/og_settings.JPG?dl=0 but it does not find the image on the page?
Forum: Plugins
In reply to: [Mobile Contact Bar] A couple of more feature suggestionsUpdating to Fontawesome 5.0 would be nice so that the Facebook Messenger icon would be available 🙂
Forum: Plugins
In reply to: [Mobile Contact Bar] mailto not working on androidI’m answering this to myself. So the problem seems to be that for some reason on my phone (Huawei, Android 7), browsers do not pick up the default email setting (I use Google Inbox) but instead always route mailto to the default Email app which I did not have setup as I never user it.
Fair enough, thanks for the update. The only problem is that qtranslate is so very convenient for editors when it actually works ;-).
So for the pro version, if I would run into some issues with specifically qtranslate, I might expect some support?
Actually I have to correct myself on this one, for some reason the title shows OK on the english version but not on the default (Finnish) version. So yes, please add title also.
<meta property="og:url" content="https://dokkcopy.demo.site/vuokraa-vene/purjevene/"/> <meta property="og:type" content="website"/> <meta property="og:locale" content="fi_FI"/> <meta property="og:site_name" content="Dokk"/> <meta property="og:title" content="[:fi]Purjevene[:en]Sailboat[:]"/>Hi,
On my testsetup I have an issue only with the description which in this case is picked up from the product category description. I would assume that excerpt would be the same. Here is an example, I’ve prefixed those that are OK with an OK, the example is from a Woocommerce Product category.
`<!– ngfb meta tags begin –>
<meta name=”ngfb:mark:begin” content=”ngfb meta tags begin”/>
<!– generator:1 –><meta name=”generator” content=”NGFB 8.40.9-1/G”/>
ok<link rel=”shortlink” href=”https://dokkcopy.demo.site/en/yacht-charter/sailboat/”/>
ok<meta property=”og:url” content=”https://dokkcopy.demo.site/en/yacht-charter/sailboat/”/>
ok<meta property=”og:type” content=”website”/>
ok<meta property=”og:locale” content=”en_GB”/>
ok<meta property=”og:site_name” content=”Dokk”/>
ok<meta property=”og:title” content=”Sailboat”/>
not OK<meta property=”og:description” content=”[:fi]Vuokraa purjevene ja purjehdi Suomen suojaisilla järvillä, saaristossa tai uskaltaudu pidemmälle matkalle merten yli.[:en]Charter a sailboat in Finland and sail on the sheltered Finnish lakes, in the unique Finnish archipelago or venture beyond the home shores.[:]”/>
OK <meta name=”twitter:domain” content=”dokkcopy.demo.site”/>
where is the picked up from?<meta name=”twitter:title” content=”Sailboat”/>
not OK<meta name=”twitter:description” content=”[:fi]Vuokraa purjevene ja purjehdi Suomen suojaisilla järvillä, saaristossa tai uskaltaudu pidemmälle matkalle merten yli.[:en]Charter a sailboat in Finland and sail on the sheltered Finnish…”/>
OK<meta name=”twitter:card” content=”summary”/>
OK<meta itemprop=”url” content=”https://dokkcopy.demo.site/en/yacht-charter/sailboat/”/>
OK but again wondering where it comes from?<meta itemprop=”name” content=”Sailboat”/>
Not OK<meta itemprop=”description” content=”[:fi]Vuokraa purjevene ja purjehdi Suomen suojaisilla järvillä, saaristossa tai uskaltaudu pidemmälle matkalle merten yli.[:en]Charter a sailboat in Finland and sail on the sheltered Finnish lakes, in the unique Finnish archipelago or venture…”/>
Not OK<meta name=”description” content=”[:fi]Vuokraa purjevene ja purjehdi Suomen suojaisilla järvillä, saaristossa tai uskaltaudu pidemmälle matkalle merten yli.[:en]Charter a sailboat in…”/>
<meta name=”ngfb:mark:end” content=”ngfb meta tags end”/>
<!– added on 2017-04-02T15:05:51+00:00 in 0.022316 secs –>
<!– ngfb meta tags end –>Forum: Plugins
In reply to: [qTranslate X] Problem with translating categoriesI have exactly the same problem, seems to mainly affact post type Product (Woo) when there is a specific taxonomy added. Regular Products seem to work but the cateories get messed up?
Forum: Plugins
In reply to: [Autoptimize] jquery error on console after activating Autoptimize😉
btw, I sort of had understood that there was value in using both Autoptimize and Asynch Javascript, but is there in fact any reason to use both?
Forum: Plugins
In reply to: [Autoptimize] jquery error on console after activating AutoptimizeTried 2) and the error goes away..
Forum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] Hide div in amp?When I can actually put it on the production site, I’ll be happy to do so, not quite there yet 🙂
Forum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] Hide div in amp?And also made the errors go away.
Forum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] Hide div in amp?The solution to hide the map worked OK, thanks!
Forum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] Hide div in amp?This is from the Chrome console:
Uncaught (in promise) Error: amp-iframe is already registered. The script tag for amp-iframe is likely included twice in the page. at ka.f.assert (log.js:285) at pf (custom-element.js:114) at Ui (custom-element.js:108) at Ri (runtime.js:410) at f (amp-iframe.js:575) at extensions-impl.js:202 at wa (dom.js:41) at xa (dom.js:87) at c (dom.js:86) at Ce (chunk.js:165) log.js:285Uncaught (in promise) Error: amp-sidebar is already registered. The script tag for amp-sidebar is likely included twice in the page. at ka.f.assert (log.js:285) at pf (custom-element.js:114) at Ui (custom-element.js:108) at runtime.js:407 at id (style-installer.js:59) at Ri (style-installer.js:45) at f (amp-sidebar.js:327) at extensions-impl.js:202 at wa (dom.js:41) at xa (dom.js:87) log.js:285Uncaught (in promise) Error: amp-user-notification is already registered. The script tag for amp-user-notification is likely included twice in the page. at ka.f.assert (log.js:285) at pf (custom-element.js:114) at Ui (custom-element.js:108) at runtime.js:407 at id (style-installer.js:59) at Ri (style-installer.js:45) at f (amp-user-notification.js:457) at extensions-impl.js:202 at wa (dom.js:41) at xa (dom.js:87) log.js:285Uncaught (in promise) Error: amp-social-share is already registered. The script tag for amp-social-share is likely included twice in the page. at ka.f.assert (log.js:285) at pf (custom-element.js:114) at Ui (custom-element.js:108) at runtime.js:407 at id (style-installer.js:59) at Ri (style-installer.js:45) at f (amp-social-share.js:96) at extensions-impl.js:202 at wa (dom.js:41) at xa (dom.js:87) log.js:285Uncaught (in promise) Error: amp-analytics is already registered. The script tag for amp-analytics is likely included twice in the page. at ka.f.assert (log.js:285) at pf (custom-element.js:114) at Ui (custom-element.js:108) at Ri (runtime.js:410) at f (amp-analytics.js:670) at extensions-impl.js:202 at wa (dom.js:41) at xa (dom.js:87) at c (dom.js:86) at Ce (chunk.js:165)
