I have a custom Wordpress theme that is used as a base theme for 100+ sites. A child theme for each site is used to make individual changes. I have some changes I am making to the main theme on github, but once the changes are made, I need to apply the new repo files to all 100+ sites. Is there a quicker way to do it rather than ftp into each site and update the files (current solution). This way is fine but is taking me 4-5 hours to get them all done. Just curious if anyone knows of a streamlined method or a way to push the changes to all the sites at once instead of one at a time. Thanks for any assistance!
Related
is there a possible way to work simultaneously with multiple users on a Website without overwritting the global styles. When I'm saving my changes and defining some new CSS classes they always disappear after my partner saves his changes also.
Is there a possible way to avoid this problem?
Maybe we failed at the installation and made some mistakes.
According to Oxygen's site, they do support multi-user editing.
At a guess, it may be possible to apply your own hooks so things aren't auto-generated/saved. You'd essentially create your own plugin to overwrite the functions provided by Oxygen.
How that functions, I'm not sure, but it would require "manually updating" later.
Honestly, IMO, I wouldn't try to overwrite this functionality, but instead look into local environments instead. Create a copy of the site that all your devs can use on their local machine, and then move it on to a shared/dev/staging site.
TBH, I've found Oxygen to be a bit of a step back in the DevOps life cycle, since collaboration is a task now.
The official documentation recommend using a single tab when working with Oxygen to avoid issues where one tab is saving older data than another, resulting in overwriting your new changes. The same scenario can occur when two or more users are working in Oxygen at the same time.
We have developed the plugin to support multiple user simultaneously.
http://collaboration.docs.oxyrealm.com
The plugin will update data and design instantly between multiple tabs of Oxygen Editor. So the overwrite issue is resolved since the data to save will be same and synced between the oxygen editor
I know it can be a very dummy question but I'm trying to figure out how I can develop and make changes in an already existing wordpress page (write new code, etc)? Before the changes go online, I must be able to save it somehow and I also need approval from its owner.
What is the best practice for it? It has some paid plugins also, I was thinking that I should create a parallel wordpress site exporting everything from the existing one and work locally.. how does it sound? Any suggestions?
I work on mac and use Docker.
Many thanks in advance!
Cheers!
Have a read on Wordpress Developers relating to Child Themes. Tou can get started here - https://developer.wordpress.org/themes/advanced-topics/child-themes/
This will allow you to activate a child theme over a normal theme and any changes you make to its functions.php will not be overridden when the parent theme updates.
You will just need to maintain the code incase major updates are undertaken on the parent theme.
I managed multiple wordpress sites. One of my clients has a number of small onepage sites who are using the same base theme.
Because I'm working on this theme on a regular base and want to update al the site using it, I was wondering if there's a way to use a theme from one location/ different domain so I only have to update the theme one time instead of every single site.
Ive tried tools like ManageWP, they actually work pretty nice, but it needs an extra plugin (which cannot be updated within this tool).
I could think of something like a wordpress function which says: insert url of theme folder.
Anyone think this is possible?
Thanks.
So I'm a beginner to coding and I am wondering what is the difference between building a site using wordpress (which I am not familiar with) as opposed to just hand coding from a text editor like sublime and then hosting it. Should I be using Wordpress? What exactly are the benefits? Thank you.
It all depends on what you want the website for.
I've both hand coded and used Wordpress (and before that Moveable Type) over the past 15 years. When I was doing infrequent updates to my website then hand coding was perfect. I could make it look exactly as I wanted, it had only the elements that I needed and nothing heavy in the backend to slow it all down.
When that all changed to being frequently updated Wordpress was much easier. The ability to schedule posts was one of the big things that got me into using it. If you're doing frequent updates, which, say need to post at the same time every day or multiple times in a week, but you're not necessarily available, then it's great. If you're short on time, then it's also useful because you choose once how you want the site to look then type your information and publish it. You don't need to amend any code or use FTP.
What you do lack is the personalisation. Unless you're also going to learn how to make Wordpress themes to properly personalise a Wordpress site, then you're stuck with the templates available for download. Some are great, some are mediocre and some are very simple.
My next project is to get my sports team online properly, and because there are about five or so people who would need to edit it Wordpress works for this. I can give people limited access to allow them to post/edit posts but know that because they're restricted, they're not going to break it all, unlike if I allowed them FTP access, which could be a massive disaster with people who aren't familiar with that.
You need to consider what you're really trying to achieve. If the website is really you and needs to reflect you and you don't update it relentlessly, then hand coding would be my first choice. If other (perhaps inexperienced) people are involved or you need to do things quickly, then I'd choose Wordpress.
If you want to create your first website, you should use a CMS like WordPress, because it will be easiest for you to publish content online and you will find many free plugins and themes at the wordpress website.
The main difference between a CMS like WordPress and a hand coded website is the first is not create for you. WordPress can be used in many way, but you will have to learn the WordPress codex to create your own themes and plugins.
With the hand coded, you will create a website optimized for what you need.
But you have to consider, you will have to code again each time you want to edit something, and for some features it will be a lot of work.
WordPress already include many "must have" features like seo friendly URLs, categories and tags etc..
But you can also look for another CMS, smaller than Wordpress
I'm working on a premium theme for WordPress, it's my first. My question is how modular should/can I get my code before it gets to be a problem for the server or other developers who buy my theme?
For example I have 3 custom post types with taxonomies and custom column headings. Should they all be in one php file or can I break them up so that each post type is in its own file?
I'm thinking that for future projects more modular is the way to go so I can just drag and drop the pieces that I need for that project. I don't want to make my theme any slower though so I could use a little advise on how granular to make my files.
I've bought themes in the past that have both extremes but want to set myself up properly from the start.
Thanks.
This is an opinion request this one because either approach works and based on this information plus the fact you seem keen on individual files. I would encourage just that.
Modular approach works with themes if you plan to provide the same functionality per theme as you won't need to edit functions per theme. I would go with individual files and just put them in a folder. If one of those files has a bug you'll be quick on applying the changes to all the themes you create.
If you put all the functions in one file and each theme gets its own versions of those files due to requests etc. Then you create a little more work in that you copy and paste code. Not a lot of work but then that demands on just how much that single file changes over the years or even within some months.
There is nothing wrong with many folders and files. It won't have an effect on loading. It would take hundreds of include() or require() before it becomes an issue.