Bug Stomp
Upgrades and changes sometimes have unpredictable results, so post your bugs and glitches in here and I'll get out my trusty wrench and get to fixin'!
Posts 7,989 - 8,000 of 8,681
Posts 7,989 - 8,000 of 8,681
I'm not sure whether this counts as a bug, but in the import language center, the field for the file name isn't large enough for me to see the whole file name. All I can see is the beginning of the path.
It would be nice, as a double check things went well, if the next screen that says "Upload of Import File Complete" in big green letters, could also mention the complete file name somewhere, before I continue to the trial run.
It already tells me the file size. File name shouldn't be too difficult an addition.
It would be nice, as a double check things went well, if the next screen that says "Upload of Import File Complete" in big green letters, could also mention the complete file name somewhere, before I continue to the trial run.
It already tells me the file size. File name shouldn't be too difficult an addition.
I have created a couple of empty plug-ins that I can't edit, delete or replace. I inadvertently tried to add the plug-in while not logged in. The system puts the plug-in's name into the plug-in list, so I can't reuse the name, but does not list me as creator (since I'm not logged in) so I can't edit or delete it. The system should check log-in status before taking any action. Meanwhile, there are a couple of (Eniola_something) plug-ins with no entries and no creator listed.
I am using a regular expression in a seek
Seek: ("^[A-Za-z]$") (re)
When I tried to edit the seek, the seek field in the Language Center turned into just "(" with the rest of the expression missing.
The original line in my file is
+ ("^[A-Za-z]+$") (re) [0] <?PF raw; rem (key1) as only "name" ?>
but when I imported it the '+' was missing from the Regular Expression (']+$' became ']$'), which I assume is why the parser did not recognize 'Samantha' as a valid entry, since it is longer than one character...
Seek: ("^[A-Za-z]$") (re)
When I tried to edit the seek, the seek field in the Language Center turned into just "(" with the rest of the expression missing.
The original line in my file is
+ ("^[A-Za-z]+$") (re) [0] <?PF raw; rem (key1) as only "name" ?>
but when I imported it the '+' was missing from the Regular Expression (']+$' became ']$'), which I assume is why the parser did not recognize 'Samantha' as a valid entry, since it is longer than one character...
While editing a seek in the Language Center I got an error message:
"Keyphrases should not contain any punctuation.
Your entry has been adjusted to fit this."
(seek contained apostrophes "... My name's, my name's,...")
It apparently had no effect on the content of the seek.
"Keyphrases should not contain any punctuation.
Your entry has been adjusted to fit this."
(seek contained apostrophes "... My name's, my name's,...")
It apparently had no effect on the content of the seek.
Check to see if the apostrophe is still there some times it gets stripped out. Sometimes you have to use the slash apostrophe to get it to work.
well, the backslash went away...
Some forums where precise syntax is discussed have text boxes that are immune from html hijinks -- whatever you type into a text box is duplicated character for character with no changes.
Yeah, dream on girl...
Some forums where precise syntax is discussed have text boxes that are immune from html hijinks -- whatever you type into a text box is duplicated character for character with no changes.
Yeah, dream on girl...
In files you import, you have to duplicate backslashes anyway.
I have as Seek for the name the following line in the files:
+ my name is ([\\\\w\\\\s]+) (re) [0] <?PF raw; ?>
and the assignment of mem-name is in the answers. (Should work with both AIScript instructions in one line too, though.)
(\\w stands for "word character" (letters), and \\s for "whitespace" (space, tab, line feed/carriage return))
Maybe the double quotes make trouble?
I have as Seek for the name the following line in the files:
+ my name is ([\\\\w\\\\s]+) (re) [0] <?PF raw; ?>
and the assignment of mem-name is in the answers. (Should work with both AIScript instructions in one line too, though.)
(\\w stands for "word character" (letters), and \\s for "whitespace" (space, tab, line feed/carriage return))
Maybe the double quotes make trouble?
When my bots start a conversation, I find their initiating line twice in my transcripts. (The second time with the name of the chat partner included.)
Likewise, when someone else starts a conversation, I don't find their initiating line in my transcripts at all.
Likewise, when someone else starts a conversation, I don't find their initiating line in my transcripts at all.
Detailed Search appears to be broken. It won't leave the first 16 bots when the "Next" link is clicked. Keeps looping to the first sixteen found by the search criteria.
I've been having a lot of difficulty with "Language Center Import file". Seems I'd import something, and the Language center would not replace the old Language center with the new one, but would selectively replace key phrases and seeks and such based on differences between the old language center and the incoming file. Unfortunately, my Language Center got messed up in this process, and it wound up with statements I could not get rid of. Some were duplicates, some were near duplicates. I could export the bad file, fix it, re-import it, and the mistakes would still be there. I tried fixing it in the on-line Language Center, but that didn't work either.
I think I have found a work around. I created a stripped down import file: nothing but xkeyphrases, with minimal responses. I imported that, then imported my corrected file without duplicate lines, messed up indents and so on. Seems to work.
I think I have found a work around. I created a stripped down import file: nothing but xkeyphrases, with minimal responses. I imported that, then imported my corrected file without duplicate lines, messed up indents and so on. Seems to work.
» More new posts: Doghead's Cosmic Bar