Stuart Silvester

This table (core_widget_areas) has existed since 4.0.0, so if they're missing from your backup that may suggest that your backup is incomplete.

Thanks, this will be fixed in the next beta.

I have deleted your review, you can submit a new one now.

1 hour ago, AlexJ said:

Thanks! Is that going away or it will stay? Also any thoughts on how to download the applications? 

When the Marketplace closes you'll need to obtain any future updates from the author. Many 3rd party authors are (or already have) setting up their own websites to sell their products. With 4.7.13 you'll be able to manually upgrade resources you installed from the Marketplace.

We will be providing a 'proof of purchase' system in the near future but in the meantime authors may ask you for another proof of purchase if you want to obtain updates directly.

I would suggest solving the problem that's causing the logs to begin with. A 'large' table won't slow things down but a plugin causing something to get logged a lot could.

The table is automatically pruned, you don't need to manually clear it.

You should probably disable the 'MVN; (or similar name) plugin until it's fixed.

We've got an open bug report for this, it will be addressed in a future release.

3 minutes ago, Clover13 said:

Not possible via IPS, but an external process can be used.  I'm just trying to figure out what else has to change to get things working as they should.  I'll test out the lazy loading and page jumping impact to CLS with my current solution.

I wouldn't resize images outside of the software, the dimensions etc are stored and may cause issues.

One thing you can look at is losslessly optimizing the images whilst keeping them the same size, there are many tools available for this.

They are used for lazy loading to reduce the page jumping around as the images load in. It's not possible to rebuild attachment thumbnails for previous content though.

1 minute ago, Extrex said:

I can't find it

I would recommend checking your spam and trash folders, we sent you an email on Friday and it shows that it has been viewed.

1 minute ago, sudo said:

Until the end of October?

I mean we are all paid customers.

After October you'll need to get any updates from the author, we're not going to be allowing files to be downloaded directly, that isn't part of the agreement we have with authors. There will be a means to 'prove' your existing ownership to them on their own sites so you can continue to receive updates and renew the purchase (if required)

10 minutes ago, sudo said:

I would have hoped for a 6 month notice period to be honest not 2 1/2 months.

Considering we cant download addons any more other than through admincp we cant even back up for a wayward plugin dev who is sick or unable to handle the change in 2 months.

Please at least let us download what we own to self install for now.

5 minutes ago, Square Wheels said:

This would be helpful.

Nothing in that regard has changed yet, the only material change is that you can no longer renew any purchases. Anything you've purchased and is still active is still available.

Hi Mike,

The release of the fix was mentioned in our release notes for 4.7.3 - 

Fixed an issue preventing upgrades from really old versions.

Ultimately, upgrading from old versions is going to get less and less stable as technology goes forward. We do fix issues that come up when we're informed about them but we no longer test upgrades from such old (released almost 9 years ago!) versions of the software.

4 hours ago, David N. said:

This just occurred again just now. About 10 seconds to submit a reply to a thread. 

Actually the same is occurring when replying here. 

This won't be a problem in .13. There can be a bit of slowness if there's a delay connecting with a back-end service. We've adjusted the timeout so this won't cause big delays.

We use jQuery 3.7.0 in the 4.7.12. It looks like you've got a custom widget/block including another version of jQuery (3.3.1).

They say they've retired the test because it's old - https://www.validbot.com/tests/102/safari-pinned-tab-icon.html

Outside of that, we don't currently support SVG for favicons. Not all browsers (mainly Safari) support this.

mask-icon is a Safari specific thing, It was originally for those MacBook Pro's that had the touch bar so they could show a single color icon. I believe Safari may use it for other things.

https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/pinnedTabs/pinnedTabs.html

https://en.wikipedia.org/wiki/Favicon#How_to_use

Click check again on your license, I have just manually fixed it for both of you whilst we work on a fix.

Please go ahead and click 'check again' if you have a banner about the license expiry, or go to the license page in the AdminCP and click check again. Then you should be all set.

The date format depends on the locale of the language pack you're using. If the date format is wrong, you're most likely using the wrong locale. (en_US vs en_GB for example).

8 minutes ago, Kirill N said:

$INFO['use_friendly_urls']		=	‘1’;

This isn't using proper backticks. You can remove this line

The error suggests you're missing files, see @Jim Ms advice above.

It only happens if you have DEBUG_TEMPLATES enabled (because it bypasses the deprecation suppression in Whoops), but we'll get this fixed

Yes and no, loading="lazy" cannot work for background-images for example, which is something we use it for currently. We won't be making any changes for this in v4.

59 minutes ago, rfcontreras said:

I've didn't notice that until today. May I ask why ? Is there a workaround ? My attachements are getting bigger, backup's takes ages and I need to reduce the site footprint.

Best regards

Ricardo

Images typically have sizes hard oded in the post for lazy load purposes so changing the size of the image would make your previously uploaded thumbnails blurry

Cloudflare is caching your page with "ipsJS_none" CSS class on the body, it's likely that the cookie isn't being passed through when the initial page is cached. This means the CSS won't hide the bar on the initial load (due to how it's designed) and after the JS loads it goes ahead and hides that (although the page has been told that JS isn't supported).