#5403 - Lingering monikers

By Adam Edington
Added 28th Sep 2023, 6:23 AM
5 views

Identifier	#5403
Issue type	Minor issue (breaks specific functionality)
Title	Lingering monikers
Status	Closed (cannot reproduce)
Handling member	Deleted
Version	10.0.43
Addon	core
Description	I am trying to set monikers on catalogue categories (using roman numerals rather than years). The issue I am having is that Composr insists the moniker is already taken by a since deleted (or renamed) category. Clearing caches doesn't seem to help remedy the issue.
Steps to reproduce
Funded?	No

The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated

Comments

By Guest posted 12th Nov 2023, 4:10 PM

I could not reproduce, but I did encounter an issue seen in #5441 . Is this the issue you had... e.g. had to do with the "similar content" warning?

By Guest posted 14th Nov 2023, 3:14 PM

I've had various issues with monikers lingering after content is deleted (Chris fixed this one via a Hotfix though). Let's say I change the name of a catalogue category, I have had issues changing the moniker to reflect the change. I can enter a new one but the old one won't go away. I haven't tried via the DB as it should be doable from the edit page. When trying to reorganise things, monikers are painfully reluctant to change.

By Guest posted 17th Nov 2023, 9:08 PM

On my end, when deleting or editing a piece of content, the moniker is set to deprecated as it should be, which then allows me to use that moniker elsewhere. Thus, I cannot reproduce.

Can you provide a specific step-by-step replication case for me so I can try exactly what you are trying to do on my end? Perhaps I'm not doing things the way you're trying to do them and thus not encountering the bug.

By Guest posted 21st Nov 2023, 9:14 AM

Hey Adam.

Check https://compo.sr/tracker/view.php?id=4907 . Is this possibly the fix you are looking for? Chris made this hotfix a while ago. It has not yet made it into v10 (it's scheduled for upcoming 10.0.44).

This may explain why I can't reproduce the error if you're running 10.0.43 and I'm running directly off of git.

By Guest posted 3rd Dec 2023, 3:03 AM

Pretty sure I included all the relevant hotfixes (but not 100% sure). I mentioned the hotfix in an earlier reply but if I somehow added hotfixes in the wrong order it could well be that I don't have that particular hotfix installed correctly, On that basis, I will trust in 10.0.44 being the solution.