Ghost Fields
selfservice0 opened this issue ยท 17 comments
I posted a bug report about ghost fields a while back.
I was told to manually remove them from my database.
I checked my database and they aren't there
I used mysql and sorted by cords. None of the ghost fields were there.
The only way to remove them is by either typing "/ps clean" once per server restart (which lags the server like crap for some reason) or to find the exact cords of the ghost field, to place a new pstone over it and then remove it.
Either way they will return on a restart.
I was thinking. If they aren't in my database then why are they there?
Maybe, I use mysql and for some reason I have a "PreciousStones.db" inside the preciousstones plugin folder. Could this be the reason, maybe the fields from that .db are loaded? What is the PreciousStones.db for if I use mysql? Can I delete it safely?
Are you using any breakable fields?
/ps clean is the correct way of removing them. We sometimes get funny
conflicts with Grief Revert fields, are you using those?
On Wed, Nov 16, 2011 at 7:49 AM, selfservice0 <
[email protected]
wrote:
I posted a bug report about ghost fields a while back.
I was told to manually remove them from my database.I checked my database and they aren't there
I used mysql and sorted by cords. None of the ghost fields were there.The only way to remove them is by either typing "/ps clean" once per
server restart (which lags the server like crap for some reason) or to find
the exact cords of the ghost field, to place a new pstone over it and then
remove it.
Either way they will return on a restart.I was thinking. If they aren't in my database then why are they there?
Maybe, I use mysql and for some reason I have a "PreciousStones.db" inside
the preciousstones plugin folder. Could this be the reason, maybe the
fields from that .db are loaded? What is the PreciousStones.db for if I use
mysql? Can I delete it safely?
Reply to this email directly or view it on GitHub:
#107
Nope no breakable fields (the ghost fields are from an old version of preciousstones, I have updated to every update released since and none have got rid of them. I have grief fields disabled.
What about the PreciousStones.db what does it do. I kind of feel as it has the ghost fields in it and it is being loaded on start. Would it be safe to remove the PreciousStones.db?
It just depends on whether you're using MySQL or not.
It only loads one or the other(mysql or sqlite). It won't be getting data
from both.
On Wed, Nov 16, 2011 at 2:50 PM, selfservice0 <
[email protected]
wrote:
Nope no breakable fields (the ghost fields are from an old version of
preciousstones, I have updated to every update released since and none have
got rid of them. I have grief fields disabled.What about the PreciousStones.db what does it do. I kind of feel as it has
the fields in it and it is being loaded on start. Would it be safe to
remove the PreciousStones.db?
Reply to this email directly or view it on GitHub:
#107 (comment)
I use mysql. Well where would these ghost fields be then? I checked my mysql database and the fields aren't stored there, unless it stores the coords incorrectly.
If they aren't in the DB then they don't exist. Maybe your users are using superickaxe to remove fields? Let me know if you still have these issues
Look
http://imageshack.us/f/193/91938952.png/
As you can see in that picture there is a field in the x: 52 coord. I sorted the db by x coords and none match it.
It must be loading the ghost fields from somewhere else. I have a PreciousStones.db file in my preciousstones folder. Is there anyway it is loading that along with my mysql? Should I delete the preciousstones.db?
Going into the field and typing "/ps delete" will remove it until next server restart and it will just pop back up.
Odd, but no it would only load it from one or the other. Delete that .db file, it probably got made the first time you loaded PS without mysql.
did so, restarted server, fields back. Here is screenies.
I deleted the field
http://imageshack.us/photo/my-images/525/fielddeleted.png/
Field is gone
http://imageshack.us/photo/my-images/521/fielddeleted.png/
Restarted server, Fields back.
http://imageshack.us/photo/my-images/404/fieldisback.png/
I found the ghost field. It's inside "pstone_cuboids" table. I was checking pstone_fields.
Any idea why it's not deleting it? Well saving its deletion*
I doubt the problem is with all fields int that table, that would mean that all fields that have the flag cuboid:true turn into ghost fields when deleted.
Dunno why its happening. Ill investigate.
Maybe the field type used to have cuboid:true flag and began to be saved in pstone_cuboids but then you changed your mind and you removed it, so now the new fields of that type are stored in pstone_fields and so that created the mismatch?
I no longer have any field types with the "cuboid:" in config. Maybe that's the issue?