• Resolved Website Rob

    (@website-rob)


    Greetings,

    There are the beginnings of a great plugin although I’m finding some inconsistencies that could use some correcting. One of those I just now became aware of.

    It seems the plugin keeps its own ‘error_log’ which is good but I did not see it mentioned anywhere. As we know, documentation is a bit sparse and I’m hoping that will improve in the future.

    /wp-content/plugins/phastpress/error_log
    [25-Aug-2020 04:38:45 UTC] 37686382 images Unauthorized exception: Not allowed url: [email protected]

    In a 3 hr. period I racked up 4,000 of the above errors.

    Please advise.

    Thanks

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Albert Peschar

    (@kiboit)

    Hey @website-rob,

    The plugin does not keep its own error log. It uses PHP’s error_log function, and it looks like your server is configured to write those messages to a file called error_log in the current directory.

    Actually keeping a separate error log that is automatically emptied is on the roadmap. For now you could add a .user.ini in wp-content/plugins/phastpress file with the following contents:

    error_log = /dev/null

    This will disable the error log entirely. Alternatively:

    error_log = syslog

    This will log errors to the system log, which should be rotated automatically.

    Regarding the error itself: it seems that you have some plugin or script that’s adding this @2x to the generated image URLs. That’s causing the problem. This plugin should be disabled.

    –Albert

    Thread Starter Website Rob

    (@website-rob)

    Sorry but I beg to differ.

    PhastPress uses __p__ when rewriting images (from jpeg to webp) and because it is also trying to rewrite Retina images (the @2 tells us it is a Retina image) there is a problem somewhere.

    The error_log file also appears to be written by the plugin because if plugin is Disabled, no image recoding and no errors. I haven’t checked everything to see what connection the plugin is making with other plugins as this is a Client site and I need to move with caution.

    I know this plugin is doing some things not documented or mentioned because it also has some sort of feature to connect with Google PageSpeed. Only happened once so far, automatically, and I know it is the plugin because it provides a msg. window with two links to PageSpeed. One link appends “?phast=phast” to the end of the URL (PhastPress Enabled) and one link appends “?phast=-phast” (PhastPress Disabled) so the difference can be seen.

    A somewhat interesting feature but a bit of a surprize because the site it happened on was Apache Password Protected and PhastPress obtained the login so PageSpeed could connect and work.

    Be a good idea to get some Documentation going ASAP so people can better understand the Plugin and not have to go through any surprize features. Again, you’re off to a good start but still more work to be done.

    Plugin Author Albert Peschar

    (@kiboit)

    Hi @website-rob,

    If you have a URL to an image ending in @2x.jpg, PhastPress should rewrite that URL to something ending in __p__.jpg, not [email protected]. That means that there is a plugin or script changing the URL after it is rewritten by PhastPress.

    Would you be able to share the URL to your site so I can have a look? And which theme are you using? It is probably your theme that includes the retina.js script which changes the image URLs.

    If we can confirm that this is the case, I can update PhastPress so that it is compatible with this script.

    A somewhat interesting feature but a bit of a surprize because the site it happened on was Apache Password Protected and PhastPress obtained the login so PageSpeed could connect and work.

    PhastPress simply links to PageSpeed with your site URL prefilled. It should not pass along any authentication details.

    Be a good idea to get some Documentation going ASAP so people can better understand the Plugin and not have to go through any surprize features. Again, you’re off to a good start but still more work to be done.

    Thanks for your feedback. When things come up often, I tend to add them to the FAQ. Unfortunately, I don’t have time right now to write a more extensive manual.

    –Albert

    Plugin Author Albert Peschar

    (@kiboit)

    Hey @website-rob,

    I’ve just released PhastPress 1.71, which adds support for Retina.js. Could you update to that version, and see if that fixes the retina images on your site?

    https://downloads.www.ads-software.com/plugin/phastpress.1.71.zip

    You should be able to see in developer tools that currently those images are not loaded correctly, and that after the update, they are.

    This update should also stop the errors in the log.

    Please let me know if this update fixes the problem.

    –Albert

    Thread Starter Website Rob

    (@website-rob)

    v1.7.1 fixes the Retina error problem. Thanks.

    Curious also that the “connect to PageSpeed” pop-up showed automatically and I wonder if that is related to the WordPress version used? (pop-up=yes WP v5.5 … pop-up=no WP v5.2.7)

    Regardless of version though, there is no visible option for it?

    Thread Starter Website Rob

    (@website-rob)

    So the “connect to PageSpeed” pop-up is something I had overlooked. It is found using a mouseover of the Exclamation sign, just to the right of “PhastPress optimizations”.

    PhastPress v1.72 is working well and the Plugin is a keeper at this point.

    Plugin Author Albert Peschar

    (@kiboit)

    Hi @website-rob,

    Thanks for the update. I’m glad to hear that it is working well now.

    –Albert

    I’m also seeing lots of “Unauthorized exception: Not allowed url” errors, but in my case, the errors being triggered by normal images. For example:

    [06-Feb-2021 00:41:49 US/Eastern] 65514933 images Unauthorized exception: Not allowed url: https://www.clinicalmatchme.com/wp-content/uploads/2020/08/doctors.jpeg

    I’m using version 1.98.

    Plugin Author Albert Peschar

    (@kiboit)

    Hi @bkonia,

    This could be caused by your PhastPress cache directory being removed. In that case, previously generated URLs (in cached pages) will no longer work. These will then get redirected to the original image, so the site should still work.

    I’m not seeing any issues on your site, so I would probably ignore these messages for now.

    If you have further questions, please open a new support topic. (So that the user who created this support topic doesn’t receive notifications needlessly.)

    –Albert

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Unauthorized exception’ is closed to new replies.