jh20001

catacaustic:
Maybe a separate system can handle that. I don’t know. No matter what, something needs to be done, even if it means cracking down on plugins that are misusing the feature because they simply don’t care to play by the rules. I am so sick of the exposure to third-parties it has been causing all these years.

*(Please note, I’m not yellowing through my text or anything. Quite calm. Simply sharing what’s been continuously building in my head all these years. Not blowing up at you or anyone else..just expressing) ??

Joy:
I may start doing that myself. Sharing what I feel about this kind of thing. I have dropped plugins from the past and sought out replacements because of things like this. I don’t the userbase or third-parties being hounded for donations and stuff that they have no connection with. It chases people off, causes confusion, raises security concerns and more.

• This reply was modified 3 years, 9 months ago by jh20001.
• This reply was modified 3 years, 9 months ago by jh20001.
• This reply was modified 3 years, 9 months ago by jh20001.

Could just remove the option for contributor/subscriber roles to even be compatible with the notification system. It just doesn’t make sense to me.

or…..are there any suggestions out there? Oh the pit in my stomach is growing. Sadly I get the feeling I am in a room with no doors talking to myself. ??

Sadly, it is obvious that the plugin has been abandoned by pento. Thankfully, the author is alive and well. He is simply choosing to walk away from it (clearly). It is too bad he couldn’t mention it in the description of the plugin so others would know the confirmed fate of it.

It seems he has contributed to various things like Jetpack so he seems to still be actively involved. Hell, WP’s native updates might have been inspired by his work or maybe he even contributed to it somehow. Thankfully, WP’s own auto-updates should get better over time and this plugin should no longer be required. As long as everyone addresses these concerns with WP’s team of coders so they know the weighted interest is there for these features.

• This reply was modified 3 years, 9 months ago by jh20001.
• This reply was modified 3 years, 9 months ago by jh20001.

That is so incredibly weird and annoying.

Did you ever get a full answer for this? I too see this in one of the sites. In a month, it raised the error log over 30MB in size. That is ridiculous. I looked for keywords within the error (the spam messages) to make sure nothing exists in any of the tables within the DB as well as any of the files.

I honestly thought it was spam comments that were thankfully being blocked by Asmiket or whatever, but then I finally ran into this post.

Update: I had to finally disable this. The new version keeps trying to force dark mode now (if you slide it to off, next visit to the dashboard or any other page sends it right back to on again) and those of us with access to the Jetpack stats widget in the dashboard just want to put our fist through the screen because it annoys the eyes so much. Oh well. It had so much hope :,(

that = dead end every time. Stupid HostGator. they are too big and powerful. They don’t care about anyone’s problems lol :/

UPDATE!!: Buddy of mine solved it. He said the plugin wasn’t capable of opening error_log because it was too big for the plugin to handle efficiently, despite it only looking for the last 20 lines. Therefore it was causing a memory leak that was overwhelming everything. The memory limit is 256MB and is working out just fine everywhere else (using about 20-30% on average).

There was an Imagick version check notice that kept pinging the log because HostGator fails to keep their PHP plugins updated, which grew the log to 70MB. He added a .user.ini file and disabled the version check for now and we re-enabled the error log widget and everything is working now.

As for the Imagick, HostGator won’t do anything about that. He confirmed they would have done the exact same thing he did to work around it but not “fix” it. They are the only ones that can, so stalemate. Plugin is working again at least.

• This reply was modified 4 years, 1 month ago by jh20001.
• This reply was modified 4 years, 1 month ago by jh20001.

Update: Actually, I had to revert back. For some reason, the “preview” screen for a new post is thrown out of whack when this is in use. Switching back, the preview screen is fine. Everything else was ok (the actual submitted post and everything else). It’s just the preview page that was affected. Really strange.

I may have to try the CSS approach

This did not fix it. However, I disabled the error log widget, and all of the widgets have re-appeared on the dashboard. Submenus to the main menu are popping up on hover and everything again. So it is the error log causing troubles it seems.

This is quite odd since this had never happened before. As I mentioned, nothing has been modified/added outside of YARPP, and I don’t see how that could conflict.

Update: Works well enough, thank you. I see sometimes a title might be cut to early … (without hitting the max), but it’s fine. It seems to be rare and may only be happening when the following line after it hits the limit. Either it works and looks nice and I was able to format around it to match the theme of things. Thanks again ??

Great, thanks. I’ll give it a try. If it works, I’ll build it up to something nice. I’m good at the visuals side of things, but when it gets deeper into the code, I brace for help ??

• This reply was modified 4 years, 1 month ago by jh20001.

Yes, that’s what we were seeing, but on all of the videos. Thumbnails were set to best quality.

Hi. No, unfortunately. As mentioned, I got rid of the plugin weeks ago, so I have no examples to offer now.

Hey, yes, I completely understand how it works, but that plugin has been failing to show the images for a long time, leaving a stretched out pixelated gray default loading thumbnail in place of an image, which doesn’t give the reader any idea of what the video is or about. It isn’t even properly showing the title text over that generic image does populate. It looks tacky/terrible and had to go finally. Some say maybe it is WP Fastest Cache causing a conflict. I doubt that, but that got me thinking….who better to offer an option that actually works than you. So I threw the idea out there ??