Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: pat_speeder
Latest plugin version 1.1 with some improvements:
Better support for all kind of IE conditional comments into the <head>
part of the document;
Support for the Google comments (i.e. <!--googleoff: all--> ... <!--googleon: all-->
);
Better support for accentuated languages;
“Compact mode” added (see: plugin help) for extreme compression if needed;
Better precedence for global preference settings against plugin attributes;
Checks the server config against zlib compression before GZIP.
Textpattern 4.7 + required.
Download: http://pat-speeder.cara-tm.com/
Patrick.
Github | CodePen | Codier | Simplr theme | Wait Me: a maintenance theme | [\a mi.ni.ma]: a “Low Tech” simple Blog theme.
Offline
Re: pat_speeder
Hi Patrick,
I have dowloaded the latest version of your plugin as version 0.7.5 had some problems but the latest version does not seem to be compressing the source. I am using the tag <txp:if_logged_in><txp:else /><txp:pat_speeder gzip="0" /></txp:if_logged_in>
and checked on all my browsers, after of course I logged out from txp, but the source code looks readable on all of them.
Ok… I needed to enable it in Admin>Preferences. You do mention it but…. Well I’m blind.
Last edited by colak (2019-05-16 12:45:36)
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Online
Re: pat_speeder
I am posting again as I am doing further tests on txp v4.7.3 and pat_speeder v1.1. Basically, and for no reason I can detect, the plugin breaks the site. If you like I can send you a login should you like to test.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Online
Re: pat_speeder
Hi Colak.
Reading this: https://forum.textpattern.com/viewtopic.php?pid=318035#p318035
Is it solved or did you always got a problem with the plugin?
Patrick.
Github | CodePen | Codier | Simplr theme | Wait Me: a maintenance theme | [\a mi.ni.ma]: a “Low Tech” simple Blog theme.
Offline
Re: pat_speeder
Hi Patrick,
The problem is not solved. Your plugin seemed1 to be working just fine until a few days ago but after checking a particular page on Safari (not my default browser), I noticed the problem. With the plugin disabled, the pages look and validate OK but when enabling it in admin>preferences, the pages do not validate and they break. Below is a screenshot of this page with the plugin enabled.
1 I might be wrong as I do not see compression because I use it just for the visitors. The code I am using is here
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Online
Re: pat_speeder
The “Simplr” theme use the plugin without any problems (TXP 4.7.3; even on Safari 12 OSX Mojave).
In never noticed some problems on your website before. So, it seems that the problem occurs with the use of <txp:if_logged_in>
tags and TXP 4.7.3. Did I understand well?
I need some time to investigate..
Last edited by Pat64 (2019-05-17 10:56:52)
Patrick.
Github | CodePen | Codier | Simplr theme | Wait Me: a maintenance theme | [\a mi.ni.ma]: a “Low Tech” simple Blog theme.
Offline
Re: pat_speeder
Pat64 wrote #318078:
The “Simplr” theme use the plugin without any problems (TXP 4.7.3; even on Safari 12 OSX Mojave).
In never noticed some problems on your website before. So, it seems that the problem occurs with the use of
<txp:if_logged_in>
tags and TXP 4.7.3. Did I understand well?
I need some time to investigate..
Hi Patrick
I do not think that the if_logged_in
tags are the problem as I just checked it without them and the result is identical to the screenshot.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Online
Re: pat_speeder
Hi Patrck,
I’m just wondering if short-tags in articles have anything to do with the problem.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Online
Re: pat_speeder
I am. digging into it and I think that I found the problem. Following Oleg’s advice here I added <!---->
before the footnotes in order to avoid having a space before the <notextile />
tag. pat_speeder somehow messed up in two cases.
- It did not parse footnote 11 and the closing
<blockquote>
tag. - and following that, it skipped all content until footnote 13.
The solution is more of a hack of a hack. Instead of using <!---->
before the footnote short-tags I had to use <!-- -->
. It is a very strange bug as it did not manifest in all cases!
Last edited by colak (2019-05-18 09:23:14)
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Online
Re: pat_speeder
ps. I have discovered another little bug in the extreme compression
option, urls with rel
attribute have single spaces deleted. ie. urls like
<a href"htp://domain.tld" rel="external">
change to
<a href"htp://domain.tld"rel="external">
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Online
Re: pat_speeder
Hi Yiannis.
On the “Simplr” theme I use some rel="nofollow noopener"
with the social links into the modal box and the plugin keeps the space before the rel
attribute.
<!---->
or <!-- -->
signs the behavior can be considered as “normal”: they are treated as HTML comments and removed into the rendering code.
Patrick.
Github | CodePen | Codier | Simplr theme | Wait Me: a maintenance theme | [\a mi.ni.ma]: a “Low Tech” simple Blog theme.
Offline
Re: pat_speeder
Pat64 wrote #318100:
On the “Simplr” theme I use some
rel="nofollow noopener"
with the social links into the modal box and the plugin keeps the space before therel
attribute.
Hi Patrick
Do you use it as <a href"htp://domain.tld" rel="nofollow noopener">
or <a rel="nofollow noopener"href"htp://domain.tld">
?
For
<!---->
or<!-- -->
signs the behavior can be considered as “normal”: they are treated as HTML comments and removed into the rendering code.
I agree with you but the empty html comment breaks the source in places, whereas the one with the space does not, so the plugin might be doing something different in these cases.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Online