acekin
Forum Replies Created
-
Thank you, @bruceallen. To quote Mr. Spock, “Logic clearly dictates that the needs of the many outweigh the needs of the few.”
Cemal
I have just updated the Boost plugin to the latest version, 1.0.3, and went to the JP Boost settings. It failed to complete the scoring. I disabled my caching plugin (once more) and tried again. No dice. I’m afraid Boost does not like my site!! For the time being, I will not try Boost again. Every time I delete the cache, it takes another week or ten days to build it again. I think disabling the caching software may be necessary before building the Critical CSS. A little more clarity on this may help others who are trying to use Boost.
Cemal
I’ll be glad to. But, is there a way to share this without baring the back end of my site in public? I will share a list of plugins, settings of the caching software, CloudFlare, the theme.
Cemal
I have updated the plugin this morning and activated it. However, it has not been able to complete the site score after three tries. I am not going any further and empty the built cache at this point. Maybe after the next update.
Cemal
Thank you. I see a few more options in the plugin description images than I saw in my installation, only three. Could that be tied to the same issue?
I will now reinstall the plugin but not activate it so that I will be aware of the update.
May I also suggest a clear message, possibly in bold that before turning on the critical CSS option, the caching plugin should be stopped, and the cache be cleared as I understood after a failed attempt.
Cemal
The theme is a child theme for Genesis Framework. It is called Mai Success, a paid theme.
There were only three options, one about the CSS, a second to push the unnecessary JavaScript to the footer, and lazy load images. The current caching plugin takes care of them anyway.
Not much boost for me. Thanks. You saw the images, I will delete them now.
Cemal
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Cloudflare related issueI am writing to report that this issue has been resolved with a few simple steps. `Here are the steps I followed:
- Used a different browser, and uninstalled the Cloudflare plugin
- Cleared the entire cache of the browser from the beginning and all history, cookies, everything
- Reinstalled the Cloudflare plugin and reconnected with my e-mail and the API token
- Cleared the browser history again
- When I logged in once more, I loaded the Cloudflare plugin settings, and the “Bad Request” message did not show up
- I switched to the browser I had been using, without clearing the cache, I loaded the Cloudflare plugin settings page …
AND there was no error banner at the bottom. I visited the Cloudflare account, went to the Speed page where I saw the message that could not connect to the plugin, and the message was not there.
The initial apparent relation to WP Fastest Cache was not there after all. I thought others may want to know that it was not caused by WP Fastest Cache, and the solution was reasonably simple.
Cemal
Thank you very much, @polywogg for investigating this puzzle. I wonder if the data of creation may be Julian date and time often used in computer programming. People have an unfounded fear that if they save their JPEG files compressed, the image quality will suffer and don’t spend time on what metadata to include in the exports. I use Lightroom and export images from it but never with Lightroom XMP data with edit steps.
I wonder if a filter could be added to NextGEN upload which can optionally remove the metadata? Just thinking aloud 😉
Thank you again, Paul,
Cemal
I looked at the file in a text editor and noticed quite a bit of Lightroom edit info, like the XMP file content. They do not strip much of the unnecessary metadata and it bloats the file size. It shrunk from 870KB to 118KB after stripping the metadata. If you want to take a peek at the file, here is the download link:
Thank you,
Cemal
@polywogg nothing shows in any of the fields other than the title showing up in the first “Alt/Title” field. All the other fields are empty. I clicked in them to make sure there are no invisible characters, they were empty. I changed the title and tried to save the changes and it was blocked with an error message again.
I appreciate your spending time on this.
Cemal
Back once more! I stripped the metadata altogether from the image using an online utility. Lo and behold! It no longer breaks the Sort Gallery request. For this image, the problem is fixed. However, what part of the metadata is screwed up and how to prevent it are still points of knowledge that will be valuable to me, and probably to others. I still have the original trouble image if there is a way to perform an autopsy on it.
Cemal
I’m back. I opened the image in FastStone viewer, saved it as a new JPEG file with a new name, shorter but with spaces and one dash. As soon as I upload that image to a working gallery, I cannot click on the Sort button without getting that strange error message. Something in the file is causing it. The original file was about 875Kb, the new one I saved is about 140KB. So the size is not the problem.
There are other photographs by the same photographer, about the same size, and named similarly and they do not create a problem. By the way, I click on the Sort button to manually order them by drag and drop. It works if this image is deleted from the gallery but not while it is there.
Cemal
- This reply was modified 5 years, 1 month ago by acekin.
@polywogg, thank you for jumping in. The file is a JPEG file. The idea of it being a different file format with the jpg extension occurred to me and I saved it from the image viewing program. That did not fix the problem. I did not try renaming it, I will try and let you know. The filename has letters, numbers, spaces, and dashes. I suppose some visible or space characters may be special characters. Stay tuned. I will write again.
Cemal
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Cloudflare related issueAfter a series of trouble ticket communications with Cloudflare support and repeated trials of deactivating the WPFC plugin, the problem eventually did not stop when WPFC was disabled. At this point, I have no idea what is causing the bad request and I reported the situation to CF. I even tried the steps using a totally new browser in incognito mode to eliminate the browser cache interfering upon the recommendation from Cloudflare, no matter what I do, whether the WPFC is active or not, the bad request warning appears upon loading the Cloudflare plugin settings page.
At this point, my original observation seems inaccurate about WPFC might be the culprit. I appreciated the efforts Emre put forth, looked at it on a staging site, and could not tie it to his plugin.
Mystery continues elsewhere,
Cemal
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Cloudflare related issueI sent an e-mail.
Cemal
