Stuart Silvester

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).

8 minutes ago, Square Wheels said:

For instance, the next post link was really important to me.  I only view my site using the undread stream, then click through the unread title at the bottom. 

This was a resource intensive function, changing how this worked gave a significant performance improvement for all customers, like a really impactful performance improvement.

Trending content uses more signals than simply just how many replies it has (that wouldn't really be trending content then)

Click the link through to the PayPal Subscription and see what the status of that is, you can also look it up in PayPal to see if they have any further information about why it failed.

It does happen where payments cannot be collected, PayPal will only try so many times to capture a payment (defined by the 'Automatically Suspend Subscriptions' setting in the gateway).

Yes it's completely possible for PayPal to be late collecting a payment. I believe we allow up to 10 days for PayPal to let us know.

PayPal subscriptions work differently to other recurring payment methods, PayPal is in charge of collecting the payment according to their schedule, we cannot ask them to "charge today".

You're using PayPal subscriptions, the invoice will be created when PayPal charges the customer.

Yes, `3` means they've been excluded from archiving. Most likely because they've been archived before then unarchived.

The log suggests the image was an empty file

25 minutes ago, SeNioR- said:

From time to time I see this error in the console.

Uncaught TypeError: Cannot read properties of null (reading 'getElementsByTag')
    at $.setState (ckeditor.js?v=75e091aa041689860322:858:110)
    at $.g (ckeditor.js?v=75e091aa041689860322:852:133)
    at b.f (ckeditor.js?v=75e091aa041689860322:10:246)
    at b.<anonymous> (ckeditor.js?v=75e091aa041689860322:12:91)
    at window.CKEDITOR.window.CKEDITOR.dom.CKEDITOR.editor.CKEDITOR.editor.fire (ckeditor.js?v=75e091aa041689860322:13:285)
    at ckeditor.js?v=75e091aa041689860322:355:85

It might be related to https://github.com/ckeditor/ckeditor4/issues/5369 but it's pretty safe to say this won't be fixed. CKEditor 4 isn't going to receive any further updates.