Sorry for the late answer. Couldn't get to my computer before now.
Quote:
Originally Posted by JimmXinu
Yes. Please always include story URLs when reporting any problem. Debug log, when you have it, is also always a good idea.
|
Ok, will do. Just didn't want to clutter should it turn out to be unnecessary. Attached is everything relevant.
Quote:
Originally Posted by JimmXinu
This continues to be a problem that doesn't happen when I try. The test version includes additional debug info that might help if you can capture a debug log while it happens.
Frankly, from the complete lack of debug logs showing the problem posted, I had assumed it had gone away. (And if what I suspect is happening is true, there isn't anything I can do about it...)
|
Well, the tth thing at least turned out to be my own mistake.
Apparently I had this line under the tthfanfic.org part of the personal.ini, smack dab under my username and password:
And as you can see, with freaking indent (no idea when that mistake happened), so it thought they were a part of the username/password process too.
Since it's in the defaults I deleted them, of course, problem solved. (I'd put that there in December, when you first introduced these new changes, and forgotten to delete them now that it's turned on by default. But, did you know that those lines are marked red in the ini files as if they were an error?)
Quote:
Originally Posted by JimmXinu
I don't know what the official mobileread is policy on double posts, but I can tell you that I often don't see changes to past posts if I read them before they are changed. You got lucky this time.
|
Oops. Thanks. I'll remember next time. I keep confusing in which forums it's okay to double post and in which it's frowned on.
Quote:
Originally Posted by JimmXinu
The problem is that the order of application is in/exclude_pre, then replace_metadata, then in/exclude_pre per metadata entry.
So when the replace_metadata line for characters fetches the metadata for genre to check against 'Genii', it invokes in/exclude_pre, then replace_metadata, then in/exclude_pre for genre before doing the comparison.
Changing that now would involve a huge amount of testing that I'm not interested in doing for one corner case.
You can accomplish what you want with this instead:
Code:
[archiveofourown.org]
add_to_extra_valid_entries:,rawgenre
include_in_rawgenre:genre.NOREPL
replace_metadata:
characters=>(.*)=>\1\,Genii&&rawgenre=>Genii
exclude_metadata_post:
genre==Genii
If it's a common problem people are running into, I'm willing to consider adding code to allow for entry.NOREPL more widely to avoid having to add rawgenre. |
Dear me, no, by all means. I didn't mean it like that. No need to change it on my behalf, especially not if it's a lot of work. I just assumed that I was probably doing something wrong, and couldn't figure out what I was missing. It's not really a problem. The solution idea you offered is more than enough. (It wouldn't even be an issue in the first place if ao3 authors didn't keep adding character or ship tags into the genre field.
Half the time it's a good thing that ao3 has no limitations on the tags, the other half of the time it's a headache.)
Thank you for all your help
