Hello g00r00!

I just noticed that if you copy (/C) and paste (/P) a networked (echomail) message base in the Message Base Editor, and change your mind, so delete (/D) the copy, Mystic will clear the Export To field of the original one.

Not a biggie, but perhaps worth mentioning.

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/07 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

On 08 Aug 2021, Bj”rn Wiberg said the following...

I just noticed that if you copy (/C) and paste (/P) a networked
(echomail) message base in the Message Base Editor, and change your
mind, so delete (/D) the copy, Mystic will clear the Export To field of the original one.

Ok, that explains that! I usually just let Mystic auto-create message bases, but recently I set one base up and copied and pasted it over & over again just changing the echotag, description and filenames for each pasted base.

When I went back and looked at them some of them (but not all) seem to have shed their export to address.


Jay

... All things are possible. Except skiing through a revolving door.

--- Mystic BBS v1.12 A47 2021/08/07 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)

Hello Jay!

Thank you for your reply!

On 08 Aug 2021, Jay Harris said the following...

Ok, that explains that! I usually just let Mystic auto-create message bases, but recently I set one base up and copied and pasted it over &
over again just changing the echotag, description and filenames for each pasted base.

When I went back and looked at them some of them (but not all) seem to have shed their export to address.

Yes, I have also had that happen when setting up new areas. Like you say, it doesn't happen to all areas, so it's a bit hard to pinpoint... But at times, there is something strange going on with the Export To field.

I recall viewing the copy, with an intact Export To (of the copy), then exiting and re-entering, and the copy suddenly had an empty Export To field. Really strange.

If I come up with a reproducible test case for that I'll make sure to post it here.

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/07 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

I just noticed that if you copy (/C) and paste (/P) a networked
(echomail) message base in the Message Base Editor, and change your
mind, so delete (/D) the copy, Mystic will clear the Export To field of the original one.

Fixed!

This one kind of isn't a bug but I did change the way it works. When you copy a message base its a literal copy of the original so the "storage filename" field stays the same. This means when you delete it, its possible to also delete the data in the original base too.

I have changed it to not reset the Exports unless you answer Yes to the "Delete data files?" question that way this is less likely to happen. It
turns out I already had the file base configuration working this way!

Another possiblity to make this work better is that when you select to "Paste" I could have Mystic force you to type in a new storage filename.

--- Mystic BBS v1.12 A47 2021/08/07 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 08 Aug 2021, g00r00 said the following...

Fixed!

Brilliant! Thank you!

This one kind of isn't a bug but I did change the way it works. When
you copy a message base its a literal copy of the original so the "storage filename" field stays the same. This means when you delete
it, its possible to also delete the data in the original base too.

Ah, yes, I kind of figured it must have something to do with the copy very so similar to the original...

I have changed it to not reset the Exports unless you answer Yes to the "Delete
data files?" question that way this is less likely to happen. It
turns out I already had the file base configuration working this way!

Sounds great! Thanks again!

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/08 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)