Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • I totally agree with all of you!

    Additionally it is rather annoying to have all those styles affecting the global context and lengthening the (css-)debug output for every element everywhere. It would annoy me even if I were using the Gutenberg-Editor…

    Gutenberg should have been a plugin from the start instead of cluttering the core.

    • This reply was modified 2 years, 1 month ago by idad5.
    Thread Starter idad5

    (@idad5)

    @diondesigns thanks for your info.

    Reverting to PHP 7.4 is not an option for me right now. Also I won’t get into compiling my own DLL soon.

    I’m an architect by education and I started programming at 13 – nearly 40 years ago. My business nowadays is mainly designing, building and maintaining websites and related projects. Also I’m a father of three and I shouldn’t take the time to writ such a long comment, but I somehow feel like it right now.
    So I do consulting, designing (including a little photography and video-production now and than) I program PHP work with basic SQL, do typescript and teach CSS… and mange to stay up to date with all things web more or less successfully since 1995.
    Nothing spectacular, but all in all enough challenge for my elderly brain.
    For several reasons my main machine is a windows box (need one to see what most of my users see). I also have a MacBook Pro, iPads, an iPhone and some older android devices for testing. I tried to have a Linux-box around for some time some years ago, but it just added to my workload of keeping too much devices up to date instead of getting some work done.
    Until the early days of WordPress I used IIS for local development but at some point I had to switch to Apache (.htaccess) so I decided to go with XAMPP.

    Over time I had to make my computer accessible for my clients from outside with dyndns (balancing security against comfort etc.) and also make XAMPP work with letsencrypt, running different PHP versions for different projects etc.

    Problem with XAMPP is, that there are no up- or downgrades, if you want a new PHP version you have to do a new install and migrate all your old individual tweaks. As I do that only once in maybe 9 to 10 month automating that isn’t really worth it, also I’m still considering changing the system at some point to a better all around solution which I haven’t found yet.

    I was really looking forward to PHP 8 as I’m a great fan of strong typing since AS3 (yes I know…) and have already written several classes that way. So going back to 7.4 would break that. PHP 8 is stable for quite a while now and I’ll stay with it, as at some point I have to anyhow also I like it. Running ImageMagick and ghostscript on my own XAMPP is a benefit for my but not a necessity and I’m ok with the way it works for me right now.
    For me and probably for a lot of other people out there ‘perfect’ or even ‘right’ is sometimes not an option, ‘it works’ has to do more often than not.

    I somehow envy you for being able to do what you do, and I very much appreciate what you and other geniuses do for the community with your work. And I feel sorry when I use it in a ‘bad’ way but I have to contradict your last statement: For me the best solution for now is to run with my setting and comment out two (obsolete) lines in WP_Image_Editor_Imagick::test

    I wrote all this not only to bore you to death, but in the hopes that maybe some like minded spirits might read that and we could exchange experiences. Have a good day all of you.

    Thread Starter idad5

    (@idad5)

    Ok, by now I learned a lot more.

    In my installation there is a problem with the PLEC dll. It seems that this isn’t restricted to the latest version and not even to windows. It reports @PACKAGE_VERSION@ instead of a useful version. That was the reason wordpress woulndt use WP_Image_Editor_Imagick but gd. A bug on the PLEC side and suboptimal (9 years old) programming in the wordpress class.

    The reason why your plugin reported ghosscript as not installed however is, that you use ‘which’ to check for it and that isn’t available on windows, even if ghostscript is.

    I propose you either make clear that you plugin only works for non windows servers or you update it to work on windows. But that’s just a suggestion and I’m glad you offered it in the first place.

    Thread Starter idad5

    (@idad5)

    @diondesigns: That is true, but only in part.

    Thank you for you answer. There is an (unofficial) compiled DLL version available that works very well with PHP 8. The problem with this DLL and according to my research also with other official versions is that it reports @PACKAGE_VERSION@ as version instead of a valid version number. The problem seems not to be windows exclusive, I also read about similar problems on MacOS.

    I don’t have a clear idea yet which versions are faulty but it seems to affect several.

    While the problem originates obviously from PELC one might also argue that the check for a version greater than ‘2.2.0’ in the WP_Image_Editor_Imagick calss is less than optimal. We learned the hard way in years of browser sniffing that checking for feature is almost ever the better way tp go.

    So I would propose to that reworking the WP_Image_Editor_Imagick::test method could use a better approach after about nine years.

    Thread Starter idad5

    (@idad5)

    *Facepalm* – As I mentioned before the problem was with a totally fresh install. And I went through all the motions of starting the new (custom) theme installing the time-tested trusted plugins I need, set up the appropriate CPTs and built the advanced custom fields…
    All the while I forgot to activate my custom theme as I didn’t look at the frontend – which I didn’t start to build…

    Well I did activate my them now and: everything works as expected.

    Thread Starter idad5

    (@idad5)

    I did some more research:
    It does work (using the exact same code) with another site. Difference is that this site war updated to 5.6 where as the site I have the problem is setup with a newly downloaded WP 5.6.
    I deactivates all other plugins, the problem still persists. Strange thig is, that the background of all TinyMCE fields (also ACF filds when activated) have a light green background that isn’t caused by any editor-css I use.

    I’m really grateful for any hints

Viewing 6 replies - 1 through 6 (of 6 total)