I finally separated core sync functionality into the simple plugin. The main goal was to minimalize core changes for easier updates.
I finally separated core sync functionality into the simple plugin. The main goal was to minimalize core changes for easier updates.
I finally separated core sync functionality into the simple plugin. The main goal was to minimalize core changes for easier updates.
Nice one J, so if i understand this right i could place a plugin on github and changes made by me can be distributed everywhere... can it also sync themes?
Themes are next on list. I use it mainly for switching between core version - on locahost I have installation with full data (like forum, download, news, users), when testing theme, I sync with 2.3.2 repo (created by me) and then sync with core repo (latest developer version). From my repo I deleted some core plugins and I put them to separate repos. If I need them, then I sync with their repo and download. Or if I use core version but my plugin is different, I sync with core and then I override f.e. forum with my repo version.
I will add theme's sync when I have more AYRO UI themes for sure.
I am sure it can be written better way but this is most I was able to do. Core (real) developers use direct git synchronization, but it is not allowed on my hosting.
