ab-tools
Forum Replies Created
-
Hello Stefan,
it is a bit strange/annoying then that this issue here is constantly marked as “resolved”, while this bug apparently is not resolved yet…
This bug is rather critical for us. If you tell me that it get fixed short-term if we subscribed to your paid service, we would even consider that!
Best regards
AndreasHello,
I see that this issue got marked as “Resolved” here which is great to see!
Could you please confirm in which version of PPOM this bug is fixed?
Best regards
AndreasHello Poonam,
thanks a lot for your quick reply again, we are then looking forward to a fix soon. 🙂
Best regards
AndreasHello Poonam,
first thanks for your quick reply which is appreciated!
I saw that after your post there were a few minor updates to the PPOM plug-in and the changelog description sounded like it might contain a fix for this, but I just tested with version 33.0.10 and it is still broken.
Can you confirm if you would expect this to be fixed with the latest 33.0.10 version or your development team is still working on a fix for that?
Best regards and again thanks for your support
AndreasHello Christian,
first a happy New Year to you!
Honestly, I’m a bit surprised to see that this topic is somehow marked as “Resolved” now.
It is not resolved, I still see this issue.Best regards and looking forward to a reply from you, thanks
Andreas- This reply was modified 1 year, 5 months ago by ab-tools.
Hello Christian,
first thanks for your quick reply, appreciated!
I’ve tried just copying the HTML code directly, but despite I use the HTML editor (not the visual one), WordPress always adds a “<pre>” around the code I enter which just displays the code again instead of executing it.
When I use the “[language-switcher]” tag, it does execute the code at this location, just shows the code to the user additionally.
When I copy in the HTML code directly, it does not even execute it, just shows it to the user…
Is there any way to work around this issue?
Best regards and thanks again for your support
AndreasOK, I found out what the issue is, but don’t have a good solution for it:
When I add “[language-switcher]”, WordPress decides that it would be a good idea to add a “<p>”-Tag around it. Looks like this is not working well due to that.What is the best way to prevent that?
Thanks
Andreas… for whatever reasons it does not upload the screenshots, but it simple shows this JavaScript as visible(!) browser output right next to the flags:
// need to have the same with set from JS on both divs. Otherwise it can push stuff around in HTML var trp_ls_shortcodes = document.querySelectorAll('.trp_language_switcher_shortcode .trp-language-switcher'); if ( trp_ls_shortcodes.length > 0) { // get the last language switcher added var trp_el = trp_ls_shortcodes[trp_ls_shortcodes.length - 1]; var trp_shortcode_language_item = trp_el.querySelector( '.trp-ls-shortcode-language' ) // set width var trp_ls_shortcode_width = trp_shortcode_language_item.offsetWidth + 16; trp_shortcode_language_item.style.width = trp_ls_shortcode_width + 'px'; trp_el.querySelector( '.trp-ls-shortcode-current-language' ).style.width = trp_ls_shortcode_width + 'px'; // We're putting this on display: none after we have its width. trp_shortcode_language_item.style.display = 'none'; }The flags are working, but why this JavaScript code is shown to the user?
Best regards
AndreasForum: Plugins
In reply to: [Public Post Preview] [Plugin: Public Post Preview] Link expirationHello Dominik,
thanks again for your fast reply and support!
I’ve updated now to your developer version and added this function to my theme template:
add_filter( 'ppp_nonce_life', 'ds_nonce_life' ); function ds_nonce_life( $seconds ) { return PHP_INT_MAX; }This should fix it now.
Anyway, I still think a simple checkbox on a plug-in option page would be much better and easier to use.
Additionally I would suggest to warn the user that this link will expire by default: as I never would have thought that this preview link expires (as it makes no sense in my opinion), I was very surprised when I got a complaint from my reviewer that the link I sent to him one day before did not work anymore…
Best regards and thanks again for your support
AndreasForum: Plugins
In reply to: [Public Post Preview] [Plugin: Public Post Preview] Link expirationHello Dominik,
first thanks for your quick reply!
If I would apply this filter as you wrote, wouldn’t this affect all WordPress plug-ins?
If that’s the case, this obviously would not be a very good idea, because maybe some plug-ins really need this for security reasons.
But I absolutely don’t see why this public preview link needs to expire as I
1. explicitly enable the link (and I can disable it again at any time) and
2. this is not a public link, but I only send it to few people directly (that should review my post) and I want it to be active till I disable it again or I just publish my post.Therefore there is no need for automatic expiration – at least there should be an option to disable it.
Best regards and thanks again
AndreasHello resting,
if you like you could ask Google/Facebook/Twitter if there is a way to reset the counter – but I guess not.
So the only option would be to change the URL (permalink) of your post. This should also reset the counter.
Best regards
Andreas
[signature moderated per forum policy]Hello,
yes, I’m very sorry for that:
but this issue is fixed already now.Anyway, thanks again for your post!
[sig removed]
Hello redcocker,
I’m very sorry for this issue:
there was a problem with the ZIP file of the last update.Please do the following steps:
– manually delete the folder “/wp-content/plugins/facebook-twitter-google-social-widgets/” with a FTP program.
– reinstall new version 1.3.4 of the plug-in from WordPress.After that all your settings will be restored automatically and it will work again as normal.
Best regards and sorry for that again
AndreasHello redcocker,
thank you, I’ll update your translation in the next update.
Best regards
Andreas
http://www.ab-weblog.con/en/Hello SWOS,
after reloading your page (pressing F5) all Google+ widgets are displayed correctly.
So if they are sometimes not displayed, this is an issue of the Google+ widget itself and my plug-in.
Best regards
Andreas
http://www.ab-weblog.com/en/