Live Update 4.0.1

[Kerby]

Will be doing this in a few minutes after a bit more testing

View attachment 127699
View attachment 127700

I really wish I had more information available than just the number of conversations/alerts, but this will do I think

Is it possible that not just the number but also the alert text or conv title/lastpost-author is shown in notification?

 

[Chris D]

Nope. It works using the data exposed by XF which is simply the counts. I don't really want this add on to be complicated by returning additional data.

 

[estranged]

I have also noticed that users can't register.

Zend_Db_Statement_Mysqli_Exception: Mysqli statement execute error : Data truncated for column 'liveupdate_display_option' at row 1 -

 

[Chris D]

This is similar to the other report.

Was this a clean install of the beta version or an upgrade from version 4.0.x?

 

[estranged]

I had uninstalled the old version and reinstalled the beta in an attempt to fix the previous issue I have reported today. That means it is a clean install I guess.

 

[estranged]

Are you going to provide a quick fix for the registration issue or should I uninstall this and install the old version again?

Thanks.

 

[Chris D]

Incoming ...

 

[Steve F]

@Chris D , I just installed this fresh on PE. The defaults in the ACP options are all checked but when viewing my preferences page none are checked by default. Should they be?

 

[Chris D]

There is a new permission to control whether users can change their preferences or not so you will need to set that permission accordingly if you wish to allow those preferences to be set by users.

 

[Steve F]

It is set to allow but the options in the preferences were not checked by default. I guess what I'm getting at is upon first install I had Russ send me a convo but it did not show in the tab and no notification. Check the permission and set it to allow, went back to preferences and none were checked.

 

[Chris D]

Ah, yeah it seems the defaults haven't applied; I'll sort that.

 

[Steve F]

Also not sure why, never figured it out on the previous version of Live Update but we get x10 added to the tab/title indicator.

 

[MasonK]

I've just given this a try, and I can't reproduce the issue. Can you reproduce it consistently?

Yes. I'll download the update later when I get a chance and let you know if the issue still persists.

 

[Steve F]

Also not sure why, never figured it out on the previous version of Live Update but we get x10 added to the tab/title indicator.
View attachment 128553

Disregard, it seems to be style related. Will try to track it down...

 

[Steve F]

Chris it seems this breaks various things that use JS in styles such as ours from PE and UIX but it only does it while logged in, if logged out JS is fine (floating nav is one). You can see it on XenResources but the bug is only on mobile as well, works fine on desktop...

 

[Chris D]

XR.com was still running the first beta because I forgot to update it. I just have updated it and it's working fine for me.

 

[Steve F]

Not sure if @The Sandman is running the most recent but it was brought to my attention there. Also, running the latest on our site, https://GamerExit.com, and the scroll to top/bottom buttons and floating nav do not work unless the add-on is disabled or logged out.

 

[Chris D]

The scroll to top and bottom buttons work fine for me on TAZ on mobile too.

Am I missing something required to reproduce it there?

Maybe explain what's happening and the steps to reproduce from the beginning so I'm not missing anything.

 

[Steve F]

Are you logged in? Everything works as expected logged out, other than that those things just don't work. Unless maybe we're somehow not getting the updated JS for live update, I did clear website data and hard reboot my iPhone 6. iPad works fine so it is really coming down to viewing resolution. If you've updated XR then I'll try again but I have confirmed it on 3 sites running the most recent version.

 

[Chris D]

Yes. I do suspect it is browser cache. I think The Sandman had similar issues.

If someone logs in to the Admin CP and increases the last JS update date that should fix it for everyone.