My Authors Activity & Archive page broken

[AccelarVester]

Since the "upgrade" to the My Authers pages nothing is working as advertised.

1) New Activity does not show all new works. FYI, the Lates Works button shows the number 68 but only 10 entries are listed even if the Load More button is selected.

2) the archive link starts with stories starting on the 20th. (Today is the 27th). I'm guessing there are 58 missing entries. (68 advertised - 10 shown as new)

Is the a "go back to what works" feature?

 

[TheWritingGroup]

All you do is put in feedback. It does seem that Manu reads it: https://www.literotica.com/stories/memberpage.php?uid=81387&page=contact

 

[AccelarVester]

All you do is put in feedback. It does seem that Manu reads it: https://www.literotica.com/stories/memberpage.php?uid=81387&page=contact

Nope - changing to no beta didn't change the behavior of the author activity function.

Ugh.

 

[opklompen]

Anybody else has problems with the ¨load more¨ button no longer working?

 

[Britva415]

Has anyone https://literotica.com/faq/miscellaneous/report-bugs?

 

[gunhilltrain]

Since the "upgrade" to the My Authers pages nothing is working as advertised.

1) New Activity does not show all new works. FYI, the Lates Works button shows the number 68 but only 10 entries are listed even if the Load More button is selected.

2) the archive link starts with stories starting on the 20th. (Today is the 27th). I'm guessing there are 58 missing entries. (68 advertised - 10 shown as new)

Is the a "go back to what works" feature?

I thought Grammarly was not dependent on Literotica in any way. It seems to be affected by which browser was used when it (Grammarly) was installed. In this case it was Firefox, but the new computer only had Chrome as built. So it's sort of backwards, perhaps.

 

[ElectricBlue]

I thought Grammarly was not dependent on Literotica in any way. It seems to be affected by which browser was used when it (Grammarly) was installed. In this case it was Firefox, but the new computer only had Chrome as built. So it's sort of backwards, perhaps.

I think you've jumped threads, Gunhill. Your Grammarly query is over there, somewhere ----->

 

[gunhilltrain]

I think you've jumped threads, Gunhill. Your Grammarly query is over there, somewhere ----->

Thanks, you are correct.

 

[ZBSKRN]

Anybody else has problems with the ¨load more¨ button no longer working?

me

 

[Rictor86]

Anybody else has problems with the ¨load more¨ button no longer working?

Me as well. Also, the Archive only shows stories from Oct 20 and earlier.

 

[opklompen]

Same problem here. Ive put in a bug report, but no reply / fix of the problem. Whats the point of following authors if the feed doesnt work propperly??

 

[opklompen]

I follow a lot of authors, so the feed of new stories should contain a lot of info. Pressing "load more" still doesnt work, so i dont get to see all new stories from the people i follow! Please fix this problem

 

[TheWritingGroup]

Bug reports are far more likely to be read (we think) if they go directly via the bug form: https://www.literotica.com/faq/miscellaneous/report-bugs

--Annie

 

[TheWritingGroup]

And now, I just noticed that the "Latest activity" feed had not updated, so I refreshed the page.

New notifications appeared, two of our stories being added to someone's Favorites, three new people following us, one story published by another author we follow. Yay!

And the little Latest count jumped from (63) to (180). Works activity jumped from 45 to 97. I am not a professional arithmetician, but ....

Yes, I'm about to use the bug report form to report this.

--Annie

 

[opklompen]

I posted a bug report about this 2 weeks ago.
The load more button is still not working

 

[theMasterBaiter]

I also have this issue, and being a web dev and a huge (not that way) nerd, I dug a bit deeper. The problem is that the script that runs when you press "Load More" is requesting a url through the site api, and passing in a parameter called "last_id" which is being rejected by the server. For example:
`https://literotica.com/api/3/activity/authors?params={%22chunked%22:1,%22limit%22:10,%22last_id%22:%22019bb0c5-ac7a-734a-abe2-4d8eb6ac0207%22}`
Gets a response of 400, with a message: `{"success":false,"message":"Check query parameters. The last id must be a number."}`
And there is the issue. The last_id is being passed as a string. e.g. it has quotes around it. Those are the %22 characters. If you take those OFF, (despite it not actually being a number) it does then work: e.g. in the above example the following is correct:
`https://literotica.com/api/3/activity/authors?params={%22chunked%22:1,%22limit%22:10,%22last_id%22:019bb0c5-ac7a-734a-abe2-4d8eb6ac0207}`
(see no %22 or " before the 019b... and none after the 0207.

So if we track back in the script, it's this function that triggers the error:
```
const hi = async (s, e, t) => {
if (!Nd())
return fetch(s, e);
await Yl();
const i = dg();
i && e.headers.set("Authorization", `Bearer ${i}`),
e.token && !t ? e.credentials = "omit" : e.credentials = "include";
const n = await fetch(s, e)
, o = (n.url ? new URL(n.url) : new URL(s)).hostname;
return n.status === 401 && o.match(/literotica.com$/) && await Yl(),
n
}
```
When it does the ` const n = await fetch(s, e)` but it's the value of s which causes the problem. And s comes from func ne, and that gets it from func tg:
function tg(s) {
for (const e in s)
return `?params=${JSON.stringify(s)}`;
return ""
}
were s is being stringify'd and that's what puts the quotes around the attribute for last_id.

So the bad version of a fix would "fix" that before returning the stringify'd version of s, but the last_id is NOT a number and the API really should be accepting it with quotes around it.

The real fix is to update the API to expect last_id to be a string. And I can't help with that (unless I had access, which I don't expect) because it's in the backend code for /api/3/activity/authors

Hope that helps. And I did submit a bug report with those details.

 

[Virmian]

Just chiming in to report that it isn't working for me either.
But there is a bad workaround. https://www.literotica.com/my/#/activity/all does work and loads history further. It's a bit more cluttered, but your stories updates are in there.

 

[PublishedEroticaWriter]

And now, I just noticed that the "Latest activity" feed had not updated, so I refreshed the page.

New notifications appeared, two of our stories being added to someone's Favorites, three new people following us, one story published by another author we follow. Yay!

And the little Latest count jumped from (63) to (180). Works activity jumped from 45 to 97. I am not a professional arithmetician, but ....

Yes, I'm about to use the bug report form to report this.

--Annie

Good luck with that. I sent bug reports months ago. I have tried every way I can think of to reach them. I even discussed it in a submission I sent under author notes. I tried to send Manu a direct message. I tried the feedback option. Nothing has changed.

 

[PublishedEroticaWriter]

I also have this issue, and being a web dev and a huge (not that way) nerd, I dug a bit deeper. The problem is that the script that runs when you press "Load More" is requesting a url through the site api, and passing in a parameter called "last_id" which is being rejected by the server. For example:
`https://literotica.com/api/3/activity/authors?params={%22chunked%22:1,%22limit%22:10,%22last_id%22:%22019bb0c5-ac7a-734a-abe2-4d8eb6ac0207%22}`
Gets a response of 400, with a message: `{"success":false,"message":"Check query parameters. The last id must be a number."}`
And there is the issue. The last_id is being passed as a string. e.g. it has quotes around it. Those are the %22 characters. If you take those OFF, (despite it not actually being a number) it does then work: e.g. in the above example the following is correct:
`https://literotica.com/api/3/activity/authors?params={%22chunked%22:1,%22limit%22:10,%22last_id%22:019bb0c5-ac7a-734a-abe2-4d8eb6ac0207}`
(see no %22 or " before the 019b... and none after the 0207.

So if we track back in the script, it's this function that triggers the error:
```
const hi = async (s, e, t) => {
if (!Nd())
return fetch(s, e);
await Yl();
const i = dg();
i && e.headers.set("Authorization", `Bearer ${i}`),
e.token && !t ? e.credentials = "omit" : e.credentials = "include";
const n = await fetch(s, e)
, o = (n.url ? new URL(n.url) : new URL(s)).hostname;
return n.status === 401 && o.match(/literotica.com$/) && await Yl(),
n
}
```
When it does the ` const n = await fetch(s, e)` but it's the value of s which causes the problem. And s comes from func ne, and that gets it from func tg:
function tg(s) {
for (const e in s)
return `?params=${JSON.stringify(s)}`;
return ""
}
were s is being stringify'd and that's what puts the quotes around the attribute for last_id.

So the bad version of a fix would "fix" that before returning the stringify'd version of s, but the last_id is NOT a number and the API really should be accepting it with quotes around it.

The real fix is to update the API to expect last_id to be a string. And I can't help with that (unless I had access, which I don't expect) because it's in the backend code for /api/3/activity/authors

Hope that helps. And I did submit a bug report with those details.

It will probably be ignored like everyone else's.

 

[UnpublishedEroticaWriter]

I also have this issue, and being a web dev and a huge (not that way) nerd, I dug a bit deeper. The problem is that the script that runs when you press "Load More" is requesting a url through the site api, and passing in a parameter called "last_id" which is being rejected by the server. For example:
`https://literotica.com/api/3/activity/authors?params={%22chunked%22:1,%22limit%22:10,%22last_id%22:%22019bb0c5-ac7a-734a-abe2-4d8eb6ac0207%22}`
Gets a response of 400, with a message: `{"success":false,"message":"Check query parameters. The last id must be a number."}`
And there is the issue. The last_id is being passed as a string. e.g. it has quotes around it. Those are the %22 characters. If you take those OFF, (despite it not actually being a number) it does then work: e.g. in the above example the following is correct:
`https://literotica.com/api/3/activity/authors?params={%22chunked%22:1,%22limit%22:10,%22last_id%22:019bb0c5-ac7a-734a-abe2-4d8eb6ac0207}`
(see no %22 or " before the 019b... and none after the 0207.

So if we track back in the script, it's this function that triggers the error:
```
const hi = async (s, e, t) => {
if (!Nd())
return fetch(s, e);
await Yl();
const i = dg();
i && e.headers.set("Authorization", `Bearer ${i}`),
e.token && !t ? e.credentials = "omit" : e.credentials = "include";
const n = await fetch(s, e)
, o = (n.url ? new URL(n.url) : new URL(s)).hostname;
return n.status === 401 && o.match(/literotica.com$/) && await Yl(),
n
}
```
When it does the ` const n = await fetch(s, e)` but it's the value of s which causes the problem. And s comes from func ne, and that gets it from func tg:
function tg(s) {
for (const e in s)
return `?params=${JSON.stringify(s)}`;
return ""
}
were s is being stringify'd and that's what puts the quotes around the attribute for last_id.

So the bad version of a fix would "fix" that before returning the stringify'd version of s, but the last_id is NOT a number and the API really should be accepting it with quotes around it.

The real fix is to update the API to expect last_id to be a string. And I can't help with that (unless I had access, which I don't expect) because it's in the backend code for /api/3/activity/authors

Hope that helps. And I did submit a bug report with those details.

Maybe you should submit it as a 'story' to make sure they read it. If that part still works. I had to make a new account because my stories get stuck in pending. Start with The last id must be a number. Maybe dumb it down for them since they know nothing about coding. I know very little about coding, but I know if it isn't plug and play, you need to change the script to work with the software.

 

[theMasterBaiter]

This appears to be fixed! Thanks to the people who maintain this wonderful site.