Jump to content

Search the Community

Showing results for tags 'dbpass'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Situtation: website has been running for years without problems. We are implementing changes and setup a "dev" subdomain to be able to compare old and new. What went wrong: the hoster makes it possible to change the MySQL dbUser password. Which I accidentally did. Now the new password is not the same as the one defined in the config.php file under "$config->dbPass = ..." and the CMS cannot access the DB anymore. Nothing is working anymore! Assumptions: in config.php under "$config->dbPass = " the string saved is the salted hashed password, i.e. "myFreaking$difficultPassword" would be saved as f.ex. "jfeime7??6$$3!2". Is that right? What I need to be able to do: how can I generate that salted hashed password from the plain text password I entered on the host's webinterface for the dbUser? Or: do I just need to set "$config->dbPass" to the plain text password I entered on the hoster's webinterface to change de dbUser Password?
×
×
  • Create New...