Title: [Plugin: Glossary] Feature Req: Do not hardcode GUIDs
Last modified: August 19, 2016

---

# [Plugin: Glossary] Feature Req: Do not hardcode GUIDs

 *  [Casemon](https://wordpress.org/support/users/casemon/)
 * (@casemon)
 * [16 years, 6 months ago](https://wordpress.org/support/topic/plugin-glossary-feature-req-do-not-hardcode-guids/)
 * Hope someone sees this…
 * Following [a recent post](http://wordpress.org/support/topic/335874?replies=2),
   seems this plug-in hard-codes GUIDS in the database, such if you change the host
   name (i.e. working on development server) then all the Glossary links point to
   the old hostname and there is no Dashboard facility for updating this…
 * I know I can iterate through and replace all the GUIDS in the db when mirroring
   the production server to the development server, but this is a pain and can introduce
   problems.
 * Currently, Glossary is the only problem plug-in that requires this, so would 
   prefer to see it play nicely with hostnames rather than me have to update my 
   db mirroring flow.
 * Is there a reason it doesn’t just take the “DB_HOST” variable? I haven’t jumped
   into the PHP, but if it used the DB_HOST var instead of hard-coding the GUIDS,
   the plug-in would be more future proof.
 * Thanks for this cool plugin just the same!
 * [http://wordpress.org/extend/plugins/automatic-glossary/](http://wordpress.org/extend/plugins/automatic-glossary/)

The topic ‘[Plugin: Glossary] Feature Req: Do not hardcode GUIDs’ is closed to new
replies.

 * 0 replies
 * 1 participant
 * Last reply from: [Casemon](https://wordpress.org/support/users/casemon/)
 * Last activity: [16 years, 6 months ago](https://wordpress.org/support/topic/plugin-glossary-feature-req-do-not-hardcode-guids/)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics