I’m trying to develop a custom Wordpress starter theme with Gulp built in. Seems like the file structure of a Gulp project (with its src and dist folders) doesn’t jive with that of a Wordpress theme, which seems to want all the php files in the root directory of the theme.
Am I supposed to develop the theme outside of Wordpress, then move the contents of dist/ into wordpress/wp-content/themes/ after running the build task? Or is there a better way?
You CAN develop outside of on one localhost directory and then output the files into another directory, but it would complicate the process. It's better to work in the same directory, newly output file will replace the old one and that's about it.
Related
I'm trying to translate a plugin I published to the WordPress marketplace, but I'm having trouble.
I created the.pot file, compiled the.po and.mo files, and placed them in the /languages folder at wp-content/plugins/name-of-the-plugin. This is only translating the plugin description, it does not translate the plugin setting page that is created when the plugin is installed.
If I copy .po and .mo file and place them under this path: wp-content/languages/plugins/name-of-the-plugin then everything gets translated.
How can I manage to place these translation files automatically into this path (wp-content/languages/plugins/name-of-the-plugin) when someone installs the plugin?
Or please let me know if I'm missing something in this process?
Where would I download Git on my Local Wordpress Environment So then I can create a branch and use it as a type of test environment. and have access to the other themes?
If you are looking to test plugins and themes, it's most likely that your working directory should be established in /wp-content - it contains both /plugins and /themes. You'll want to make sure you have a .gitignore file that only tracks what you're working on.
If you are looking to work on changes to core, your working directory will almost always be the top-most WordPress root. That way, you can track WordPress/WordPress.
Actually I put my GitHub folder in my themes folder and then I could use the repos in my GitHub folder on my local host WordPress site
I have wordpress installed on the root of my website (say example.com/), but there is a folder of the website that i want to directly build in php/html not controlled by wordpress - basically I want it to be its own separate entity, but with the url being example.com/folder/, so it sits under wordpress in the url hierarchy, but is completely independant... Is that possible? I have done some research but cant find a solution or any reference to this.
Thanks very much for your help!
Just make the folder in the root directory of the wordpress install. Any files inside of that folder that does not declare the wp-load.php file will not be controlled by wordpress.
I would like to upload a custom installation of openshift. I have installed wordpress and cloned it via git. Now I would like to add manually some plugins and push it back to openshift. Where do I have to put in my extracted plugins/themes?
I appreciate your answers!
Short answer: store your plugins and themes in .openshift.
Longer answer:
Every Openshift account has what can be thought of as a username - a long number like this:
53f1a90f500446c42053423083
Each directory structure features this number so yours:
/var/lib/openshift/53f1a90f500446c42053423083/app-root/runtime/repo/.openshift
will be different to mine:
/var/lib/openshift/12345678901234567890123456/app-root/runtime/repo/.openshift
The number gets incorporated into environment variables so that scripts will work on yours and mine equally. One of these is OPENSHIFT_REPO_DIR. On your install it will point to:
/var/lib/openshift/53f1a90f500446c42053423083/app-root/runtime/repo
on mine:
/var/lib/openshift/12345678901234567890123456/app-root/runtime/repo
Another is OPENSHIFT_DATA_DIR.
When you push changes from your local directory via git, the deploy script is run and it assembles all the wp files it needs into a directory it names:
OPENSHIFT_DATA_DIR/current
Openshift moves the 'original' wp plugins and themes folders that are created during a wp install into the OPENSHIFT_DATA_DIR/current/wp-content. It looks in OPENSHIFT_REPO_DIR/.openshift for your code and copies in any plugins and themes folders it finds there.
Net effect is to assemble the plugins and themes directories by adding yours to those that came with wp. So, your fully-assembled OPENSHIFT_DATA_DIR/current will have these in it:
OPENSHIFT_DATA_DIR/current/wp-content
/themes
/plugins
/uploads
So, anything you put in .openshift will be copied to the right place, but not altered.https://github.com/openshift/wordpress-example
I am setting up 10 new local wordpress sites. I have 10 folders all named like this:
"name-of-site.com"
Inside each is a simple file structure:
briefing files
html
wordpress
I want to set up a repository on git hub for the wp-content file but I can't find a way to create an alias. Surely the end result will be 10 different repos all called "wp-content"
How can I set up a separate repo for each wp-content folder and name it "name-of-site.com"
Is this glaringly obvious and I am being really stupid???
Why not have the top level folted, that is "name_of_site.com" be the repository, and in that folder, you can create a .gitignore file to ignore the other directories you don't want, that is, the html and briefing files (if I understand your layout correctly). That way, you're simply tracking the Wordpress content. You can even move it up a level so that only the briefing files and the HTML are in separate directories and the WP content is in the "name_of_site.com" directory.
Edit:
After your comments, I think you could do it this way:
Create repos for each site you have and put the wp-content of those sites in the .gitignore file
Create one repo for wp-content, which contains all your themes. Organize them according to your needs.
Write a simple shell script that pulls the latest theme into your site's folder from the repo in the previous step. That way, every time you update your theme, you can go to your chosen site and just synch up with the latest pushed version.
Does that make sense?