Better behavior on entry posting when over the tag limit

[azurelunatic]

Title
Better behavior on entry posting when over the tag limit

Short, concise description of the idea
Instead of giving you no errors when saving, showing no tags, but displaying tags on the edit screen when you're over the tag limit and use mixed existing and new tags on an entry, the system should handle it better.

Full description of the ideaSo

Comments

[azurelunatic]

This is related to LJSV-787.

[azurelunatic]

You can post to LJ with things that were never designed to do that, like Google Docs.

[andy]

I'm Andrew Ilyin, a SUP Engineering person -- Azz linked me to this entry in our internal task tracking system, saying that there are some good ideas in here. And indeed, there are!

I particularly like your thinking approach in that we may need to figure out a way to handle non-fatal errors [warnings] in the code handling users' requests (think XML-RPC here). I think that the "LJ protocol" module that is common to posting via web and clients should first be modified to actually throw warnings and return them to the calling object (which may be client or update.bml), and after this is done,

1). update.bml/editjournal.bml can be modified to handle the warning correctly.
2). it's up to clients how to handle this API extension; weird/outdated ones can just ignore it.
3). (shiny) editjournal.bml may choose to show a notice when it sees that not all tags were added to the entry as intended.

Thank you for your feedback!

[koulagirl666]

I wonder if there's a way to put the 'new' tags as plaintext?

[charliemc]

+1

Yes, please!!!

[azurelunatic]

Marking this as migrated, as devs have decided upon a course and are proceeding merrily.