wethas.blogg.se - Phpstorm wordpress

#PHPSTORM WORDPRESS INSTALL#
#PHPSTORM WORDPRESS PRO#
#PHPSTORM WORDPRESS CODE#

This is called “Live Link” in Local and runs through ngrok. Getting help with or displaying work to othersĪ great feature of Local that wasn’t available with VVV is the ability to provide a link for anyone else to view your local site.

#PHPSTORM WORDPRESS CODE#

Simple press cmnd+alt+L and watch your code shuffle into place. This is a great tool for quickly tidying up any mistakes you have made (missing an indent/space). This can be done by visiting PHPStorm’s preferences->editor->code style->PHP and choosing wordpress from the dropdown. Lastly, the ability to add the wordpress coding style is now something I’d be lost without. This saves so much time when hunting for the root of problems it is probably the biggest appeal of PHPStorm for me personally. If you do need to visit the codex, however, simply right click on the hook/function you want to look up and you have a link in the context menu.Īnother neat tool is the ability to jump around within your code just by shift+left clicking on functions/classes etc. It’s autocomplete for wordpress functions and hooks should really speed things up or avoid unnecessary trips to the codex. With wordpress integration enabled PHPStorm really is a dream to work with. You should now have an exact copy of your live site on your local machine with your own admin user. INSERT INTO 'databasename'.'wp_usermeta' ('umeta_id', 'user_id', 'meta_key', 'meta_value') VALUES (NULL, '1', 'wp_user_level', '10') INSERT INTO 'databasename'.'wp_usermeta' ('umeta_id', 'user_id', 'meta_key', 'meta_value') VALUES (NULL, '1', 'wp_capabilities', 'a:1:')

#PHPSTORM WORDPRESS PRO#

To do this I visit the database in sequel pro (link found in Local) and run the following (replacing databasename with the database name and checking the wp_users table for the next available user ID) I also run a query to add a new admin user for myself as I like all my local installs to use the same login details (it makes things simple!).

This is simply a case of navigating to the sites wp-content directory and dropping in all that is required from the live site (be careful of mu-plugins as some hosts like WPEngine use certain plugins that won’t play nice on a local setup).

Now the database is in place we need the content pulled in.

To do this you can run wp db drop, wp db import path/to/db.sql, wp search-replace old-url new-url From here I can utilise wp-cli to drop the default database (avoid any conflicts on import), import the live database and run a search and replace to convert all URLs over.

#PHPSTORM WORDPRESS INSTALL#

I then SSH into the install (right click the site in Local and click open site SSH) and navigate to the wordpress install directory (cd app/public).

I name this something obvious (usually the url of the live site so becomes v). (I would like to utilise blueprints here as I like to use certain plugins when developing, like debug bar and query monitor, but unfortunately these do not currently work on my system).

Firstly, add a site in local by clicking on the + icon located at the bottom left corner of the interface.

This is assuming you have the content directory for the wordpress site you wish to setup and a database copy. I allow Local to create the site first and organise my sites within the default “Local sites” directory but I have a particular method of setting up a site which keeps things simple and fast. Whenever I setup a new local site I stick to the same pattern. Note: before even starting to work in wordpress using PHPStorm make sure wordpress integration is enabled! Detailed below are a few of the ways I do things to make my workflow a little smoother using these amazing tools. With Local, the complicated stuff is all hidden away and I can focus on my work and leave the environment setup alone. This usually resulted in a fresh install of VVV rather than ever finding where I had messed up. I loved VVV but without prior knowledge of any of it’s inner workings it was a rather steep learning curve that caused plenty of frustration when things didn’t work as expected. I recently switched from VVV ( Varying Vagrant Vagrants) to Local by FlyWheel (formerly Pressmatic).