anoriell - Katarzyna Janoska
Forum Replies Created
-
Forum: Plugins
In reply to: [SVG Support] Maintain original width and height on replaced svgHi,
the difference is visible on front-end while displaying the <svg>
The scenario is:
I have an SVG image that “originally” is let’s say: 350 px by 200 pxAnd I want it to display as an image that is lt’s say: 200 px by 150 px
So naturally I would do something like:
<img class="img-svg" src="..." width="200" height="150" />And I would expect a result:
<svg width="200" height="150" ...>This way I don’t have special CSS to every single SVG image that should be displayed in some other size than the original one. I can take advantage of pure HTML.
And with these few additional lines it works just that.
This is not entirely true.
You can use Types with pure PHP (I used it like that for a really long time with nothing but success), and if you decide to buy the entire Toolset package and your licence expires nothing bad happens to your sites. All you do not get after the licence period is: access to the paid support forum and plugin updates.Everything you created stays as it is.
It is really really A LOT of images and all of them are compressed in different dimensions (sometimes 1/5 sometimes 2/5 and sometimes 3/5 set dimensions – no idea why). These images will simply not be used in any other dimension than the original one only on forum.
And besides they are ever being viewed only by this one support client and one supporter and as I mentioned there is really A LOT of them so paying for compressing all these images is just killing me.
Thank you for your answer!
I haven’t noticed that option earlier…
It solves my problem entirely. Thank you very much!I’ve found:
if (!WPAC._Options.commentsEnabled) { WPAC._Debug("info", "Abort initialization version %s (comments are not enabled on current page)", WPAC._Options.version); return false; }and I changed it to:
if (!WPAC._Options.commentsEnabled && !(jQuery('body').hasClass('category-blog'))) { WPAC._Debug("info", "Abort initialization version %s (comments are not enabled on current page)", WPAC._Options.version); return false; }And the plugin works exactly as I expected. I think it would be a really nice feature to be able to turn your ajaxed comments on in archive from options panel.
Forum: Plugins
In reply to: [Termly - GDPR/CCPA Cookie Consent Banner] Translation of custom srtingsOk, so maybe try to go to WPML->Theme localization find UK Cookie on the plugin list at the bottom of the page, check it and click ‘scan for…’ button.
uk-cookie-consent position should appear in WPML->String Translation.
If not… Well you can also try to go to WPML->String Translation and check “Auto-register strings always” option at the bottom of the page.
Let me know if it worked…
Forum: Plugins
In reply to: [Termly - GDPR/CCPA Cookie Consent Banner] Translation of custom srtingsfiterix, you have to have WPML String Translation installed.
Then you go to WPML->String Translation (the last position in menu) -> you choose uk-cookie-consent from the second select list at the top of the page.
And now underneath you should see phrases than can be translated π
Forum: Plugins
In reply to: [Scissors and Watermark] Errors while cropping imagesThank you very much for your answer.
Unfortunately, your advice didn’t help. Creating the crop for the ‘thumbnail’ first doesn’t work for me…
I also don’t use ‘Dynamic Image Resizer’…
Doe’s anyone have another idea how to solve this problem?
Hey guys, can you fix that bug already?
I’ve found three solutions for this problem:
‘%%excerpt%%’ => ( !empty($r->post_excerpt) ) ? strip_tags( $r->post_excerpt ) : mb_substr( strip_shortcodes( strip_tags( $r->post_content ) ), 0, 155,’utf-8′ ),
‘%%excerpt%%’ => (!emptyempty($r->post_excerpt)) ? strip_tags($r->post_excerpt) : wp_html_excerpt(strip_shortcodes($r->post_content),155),
and simply (this certainly works for Polish language I don’t know what about the rest of them):
‘%%excerpt%%’ => ( !empty( $r->post_excerpt ) ) ? strip_tags( $r->post_excerpt ) : substr( strip_shortcodes( strip_tags( $r->post_content ) ), 0, 155 ) ,
These solutions work for Chinese, Polish, Russian and Romanian national characters. This is a genuine proof that they are good enough to be incorporated to your plugin, isn’t it?..
The plugin was updated about billion times this week and each time I (among many others) had to edit wpseo-functions.php manually (and I have 10 or so WordPress sites so it became a huge problem!)…
Please, please, please fix this soon.