Česlav Przywara
Forum Replies Created
-
Hi Rodica,
I noticed that the new 1.0.8 version now features CHANGELOG.md file, which is cool, thanks! However, I would suggest to add == Changelog == section to readme.txt file and list all changes there instead. This way your changelog would be included as a separate subpage of your plugin page (next to Description, Installation, Screenshots etc. pages) – not only at plugin directory, but also when viewing plugin details from WordPress back-end.
Best regards,
ČeslavForum: Plugins
In reply to: [Polylang] Polylang and WooCommerceHi celebrian,
The Hyyan WooCommerce Polylang Integration does not work with the newest versions of Polylang and WooCommerce. If you’re not a developer yourself and cannot fix issues that are being reported on Github, then I’m afraid you’re out of luck in the moment.
Greetings,
ČeslavHi, I just issued a pull request: https://github.com/Arsenal21/all-in-one-wordpress-security/pull/15
The change is really simple, should be easy to review.
Greets,
ČeslavHi,
Yes, I’m still having issues – as well as others have…
I already described the problem and the way how to fix it (twice), but either you are confused by my description or don’t have time to implement it. Would it be of any use if I prepared a patch and issued a pull request on GitHub?
Greets,
ČeslavHi Ariko,
I think you came accross the same problem I already had and reported here.
The problem is the following line:
RewriteCond %{HTTP_REFERER} !^http(s)?://(.*)?\.homepage\.com/wordpress [NC]Notice the
/wordpresspart – I guess, you have WordPress installed inwordpresssubdirectory? If you remove the/wordpresspart from the line above, your images should display fine.Why the HTTP referer check blocks the images even if someone visits your own site? Because your site front-end lives under homepage.com, not homepage.com/wordpress. There is no front-end URL that begins with homepage.com/wordpress, so the referer check will always match and block any image request – even from your own site.
This is of course a bug in AIOWPSF – the HTTP referer check would work properly, if it has been done against output of home_url() instead of site_url(). Site URL should be used for handling of physical assets like CSS and JS files, not for handling of (virtual) front-end URLs – this is what home URL has been designed for.
Greets,
ČeslavI would love to have this feature in AIOWPSF too!
Forum: Plugins
In reply to: [Simple Share Buttons Light] ssbl no button images showing?Hi,
I started having the same problem recently and solution that worked for me is to edit a single line of code in
simple-share-buttons-light/system/controllers/ssbl_buttons.php(line 140):Instead of include_once:
$this->images = include_once SSBL_ROOT.'/buttons/'.$settings['image_set'].'.php';
You want to just call include:
$this->images = include SSBL_ROOT.'/buttons/'.$settings['image_set'].'.php';
The problem with include_once is that it returns true on any subsequent call instead of what is being returned from the included file, so if
SSBL_Buttonsconstructor is called multiple times within a single request (for whatever reason), the $images property is being assigned a boolean value instead of array of image data…Greetings,
ČeslavForum: Plugins
In reply to: [Polylang] How to activate "Custom post types and Taxonomies"Hi mixali,
Are you using premium version of the theme? Because the linked (free) version does not seem to have any custom post types.
Anyway, I guess the theme does not define custom types it provides as public (makes quite sense for slider post type), so Polylang doesn’t pick them as translatable by default.
You can try to use
pll_get_post_typesfilter to add such post types. Unfortunately, I don’t know the exact name of the post types provided by your theme, so you have to find it yourself: you can find it via URL in the browser address bar when you go to the admin page listing all your custom post types, it should look something like: wp-admin/edit.php?post_type=post_type_name. My guess is it will be slider or something similar.Then try to add the following snippet to your theme functions.php file, but replace both occurences of post_type_name with the actual post type name:
function mixali_pll_get_post_types($post_types) { $post_types['post_type_name'] = 'post_type_name'; return $post_types; } add_filter('pll_get_post_types', 'mixali_pll_get_post_types');Be sure to not remove the apostrophes!
Forum: Plugins
In reply to: [Polylang] How to activate "Custom post types and Taxonomies"Hello mixali,
What plugin or theme with custom post type do you use? It looks like your custom post types are not public and thus cannot be translated.
Greets,
ČeslavForum: Plugins
In reply to: [Polylang] Front-end filters for links available also on back-end?Thanks Chouby,
Your snippet does the trick, though I had to use
PLL()->pref_langinstead ofPLL()->curlang, because the latter expression returns false whenever the language filter is set to “Show all languages” (as I mentioned above).Hi,
Thank you for the answer, it’s really cool that Login Lockdown feature protects also in case of XML-RPC attacks.
Regards,
ČeslavForum: Plugins
In reply to: [Add Meta Tags] Shortcode tags in automatically generated descriptionsHi George,
Sorry for a late reply, but I finally managed to have a closer look on the issue.
I checked out how description is generated in
amt_get_the_excerpt()function and the problem happens whenever page/post content is entirely wrapped by shortcode: In such case, thestrip_shortcodes()function returns an empty string, so generated excerpt is shorter than average description length and is subsequently extended via “nasty hack” (as your comment names it) – this time including shortcode tags.To workaround the problem, I hooked into amt_get_the_excerpt_initial_content filter and run WP API
do_shortcode()function from there. I’m not sure this is the best solution, it likely hurts site performance a bit, but it works for me and thus I consider this topic as resolved.As for my other suggestion on Opengraph and Dublin Core metadata descriptions – my idea was that if automatic generation of meta description is turned off in
plugin settings, this should apply toog:descriptionanddc:descriptiontoo (even if the OG and DC metadata are set to auto-generate). But nevermind that, I realized such behavior might be quite confusing when I gave it second thought.Thanks for your time.
Kind regards,
ČeslavForum: Plugins
In reply to: [Edit Author Slug] Trying to get property of non-objectHi Brandon,
Thanks for the fix, no more notices after plugin update 🙂
Best regards,
Ch.Forum: Plugins
In reply to: [MailPoet Newsletters (Previous)] Mail Poet not Compatible with WordPress 4.3Hi semaj,
This notice is probably triggered by call to
$this->WP_Widget(PHP4 style constructor – deprecated in WordPress as of 4.3) in class WYSIJA_NL_Widget. I don’t think it has anything to do with automated content no longer being pulled in your install, it’s only a notice.Anyway, it would be nice to have this issue fixed by MailPoet devs.
Greets,
Ch.Hi Willie,
For some reason the broken code that should block right click is still being printed with both galleries.
Not sure why, but you may want to check that:
1) Shortcode of both galleries do not haveblock_contextmenuattribute.
2) You don’t have Flick Photostream plugin active (or even deactivated) with the same option (block right click) turned on – it seems that Flickr Justified Gallery reads settings from the Flickr Photostream as kind of fallback.Your other option is to try to fix the plugin yourself: go to plugin folder, open flickr-justified-gallery.php file and replace
fpDisableContextMenuwithfjgwppDisableContextMenu.Cheers,
Česlav