Hi,

please do not revert back that file.
let me investigating first.

Regards

Hi,

please check it again. I made some test, seem the issue has been resolved.
please make sure activated: "Order by last comment", and please have a look the last comment from each stream items.

Regards

Hi,

It's still not working.
A lot of info is missing.

Regards
Jonas

Hi,

could you please elaborate more for missing and not working?
and I want make sure, do you understand what mean for "Order by last comment"?

what if "Order by last comment" set to "No"? what the result?

Regards

Hi,

Sorry if I was short in my answer before.

Yes, I understand what "Order by last comment" is and we love that new function.
Our problem with scrolling came before you gave us this lovely function.

As you asked I now tested with it on at first in your answer 4 hours 10 minutes ago #166093.
Scrolling down it seems work on first and second page but in third it jumps a long time back.

Now I turned "Order by last comment" off and scrolling seems to work correctly.

Please, you are welcome to test it your self, both with it on and off.

We really like to have the function turn on and to be able to go back in history.

Regards
Jonas

Hi,

Sorry if I was short in my answer before.

Yes, I understand what "Order by last comment" is and we love that new function.
Our problem with scrolling came before you gave us this lovely function.

As you asked I now tested with it on at first in your answer 4 hours 10 minutes ago #166093.
Scrolling down it seems work on first and second page but in third it jumps a long time back.

Now I turned "Order by last comment" off and scrolling seems to work correctly.

Please, you are welcome to test it your self, both with it on and off.

We really like to have the function turn on and to be able to go back in history.

Regards
Jonas

Hi,

I made a test with "Order by last comment", I cannot find the issue. (not sure if I missing something)
if using "Order by last comment", it will like this:
- stream 1 at 1 hour ago
- stream 2 at 3 hours ago
- stream 3 at 1 day ago

user X login and put new comment at stream 3, so ther order will be like this:
- stream 3 at 1 day ago (because containing comment)
- stream 1 at 1 hour ago
- stream 2 at 3 hours ago

Regards

Hi Albertus,

That is strange.
Now when I´m testing with my own profil and a testprofil I get:

Stream 1 - hours and it seems ok
Stream 2 - I get a photo with a girl tied to a MC from 2 yeas ago and only one old comment. And a lot of posts that are months old with or without comments and likes. Some comments are 1 or 2 weeks ago but not new.
Stream 3 - almost everything is 2 years ago.
Stream 4 - everything is 2 years ago.
Stream 5 - everything is 2 years ago.
Stream 6 - everything is 2 years ago.
Stream 7 - everything is 2 years ago.

On my screen it´s not working as I believe it should.
I will soon edit the post with username and password to my test profile so you can see what I see.

I will leave the "Order by last comment" on for the time being.

Regards
Jonas

Hi,

we found a bug. complicated bug regarding this issue. need more time to make some code changes :(
for temporary, I disabled "Order by last comment"

I will back to you again with the fix.

Regards

Hi,

please check it. I put the fix at your site.
and your site using "Order by last comment".

please let me know if the issue has been fixed.

Regards

Hi Albertus,

I´m on a trip and just hade a quick look with my smal mac on a bad wifi but it´s seems to work well.

Will make a bigger test when I get back later this week.

Sunny Regards from London

Jonas

Hi Albertus,

This morning ! got info about that all of our groups and events don´t have any info where the stream normally is, it´s empty.

Since I haven´t touched anything I guess It has to do with your last fix.

The stream in the "start" seems ok as I told you yesterday.

Could you please look in to it, it´s a bit urgent because we have a big event in 9 days.

Hi,

sorry, there is an issue again with this.
for temporary I turned off Order by last comment again.

please wait for the fix.

Regards

Hi,

please check it.
it's fixed now :)

will be included at 4.2.5

Regards