Following this official guide and using the flex environment with php 7.2, I am trying to deploy to App Engine with custom plugins and themes.
These themes are not available on wppackagist, given that they are truly custom to my project.
My git repo is correctly saving the custom plugins and themes -- all composer.json based wppackagist plugins are being installed as intended.
However, for the life of me, I cannot get the deploy to include my custom files. I have additionally verified that the image uploaded to AE is the correct version, and it has been promoted to serve all traffic as intended.
Can anyone help me understand the logic that I am missing to ensure that when I deploy my app that the custom plugins and themes are built into the image?
So the answer is to not change the app output folder. Via the CLI install helper, I defined the output folder to wp_app -- it still anticipated app as the folder. Nothing was in the app folder when I created the service as wp_app being the WordPress folder. So, just keep the folder structure as-is and you will be fine.
Related
I'm in the process of programming my own static pages in moodle. It works so far, but I have the whole thing running in the local environment in its own folder in the root directory "mymoodle.com/folder/".
Now I would like to install it as a plugin on the stable instance via the dashboard/frontend, but if I understand it correctly then only works with the available plugin types => path from the docu
Is that only possible via FTP access? Or is a plugin type not listed yet or have I overlooked one?
Is there a better moodle approach than plugin type "local" ?
I have already discovered the "Static Pages" plugin, but I don't really understand how they solve the redirect from /local/staticpage/ to /static/
Local Plugin folder is the best approach, if you are creating a plugin that doesn't comes under any of the other plugin types mentioned here.
However you can shift the folder (and make appropriate changes in files to require files) under the Moodle's root directory and it should work.
Being new to Wordpress development ecosystem have few queries which I m stumbled upon currently.
Have installed wordpress and it was working as expected. Had installed a theme to the website recently to the local working copy. Also, added 2 more members to the team which was previously single person and thus made the code version controlled with bitbucket server repository.
Now, the issue is when the new developers cloned the remote repository to their local machine ( entire wordpress with installed theme ) is available. But its not working properly as the new pages/links/menus/images added are not reflecting for the other's local .
Would like to know the general thumbrules which needs to be followed while version controlling Wordpress. Is the added themes/additional code changed files etc. only need to be version controlled instead of the whole Wordpress files? In my scenario what would be the changes I need to do ( any files which I need to configure to get the latest repository code to run locally )
Would we need to version control the Wordpress including the Database?
Please advise.
Yes the main issue you have there is all the things you want are within the database. There are version control things for db but not sure how best they work... so you either export and share you db with them, or all work off a remote db from a server. You can change db credentials, including ip address etc in wp-config.
As for version control, I only save my theme in git and the wp-config etc etc... the bare minimum I can. Then I use composer https://getcomposer.org/ to pull in wordpress and make use of https://wpackagist.org/ to get plugins.
Roots did a nice introduction to composer and WordPress - where I started learning from and is worth a look: https://roots.io/using-composer-with-wordpress/
I'm using Herbert framework to develop a WordPress plugin. It recommends to set up a separate folder on a disk and symlink it to the "/wp-content/plugins/" directory.
I created a project in PHPStorm with a original plugin directory. Then I added "wp-includes" folder as external library to get all the Wordpress.
I also brought up a wordpress integration this way:
Now this is how I tried to configure the server to get this plugin debugged. That isn't working.
Can you guys please help me to debug it?
There are dozens of articles for migrating a Wordpress install TO Google App Engine, but I can't find any to migrate it FROM GAE to something like WPEngine.
I'd simply love to UpdraftPlus to do it, but I can't create a backup because the filesystem is not writeable in GAE.
I could simply use a copy of the database dump and my local version of the filesystem, but that loses all the remote uploaded images that I created.
Also, I don't really know how to "undo" many of the GAE configurations that have to do with the filesystem, uploads, database connectivity, etc. If I change the
db credentials and deactivate the GAE plugin, will my site just work?
Thanks!
Lou
For anyone else experiencing the same issue, I did the following and it was really quite simple:
uploaded the wp-content folder from the source GAE folders (on my local machine) to the new host
used the native 'export' feature in the Wordpress admin: /wp-admin/export.php
used the import feature in the Wordpress admin (you do have to install a plugin): /wp-admin/import.php
Went through and activated my theme and my plugins
Updated all my settings on all my pages
Then I had to edit my function.php and header.php files as they included a few hardcoded references to IDs (posts, pages, categories).
After that, it was done!
I am wanting to locally develop a suite of WordPress plugins and widgets. My development environment consists of Windows v8.1, Netbeans v8.0.2 and XAMPP v5.6.3.
I've configured Netbeans and PHP to use XDebug. I've spent the entire weekend watching and reading various tutorials on setting up Netbeans IDE for developing a WordPress plugins/widgets.
Everything seems to be working at this point - I've been able to create new Netbeans projects by opening existing/installed plugins of my WordPress install. I am able to set breakpoints and trace through code. All seems to be working well, but I am puzzled regarding the 'proper' way to setup a new project.
Should a plugin/widget project somehow include the WordPress core files starting at .\htdocs, or should the root of the project be .\htdocs\wp-content\plugins\myplugin? In other words, should I be able to see .\wp-admin and .\wp-includes in my project tree?
My thinking is that Netbeans needs to somehow be able to read the core WordPress files to provide function reference during development of the plugin/widget and this would require including the WordPress core in my project, somehow.
Maybe my question is best asked this way:
What should the root project folder be set to for developing/debugging a plugin named MyPlugin?
and/or:
How are WordPress core files included/referenced in the MyPlugin project?
Anyone have a good step-by-step reference that would enlighten me on this?
I'm searching for this too, but here's how I set it up. I'm developing a theme (plugin would be analogous) so I have the theme source and NetBeans project files in a separate folder outside of WordPress folder, and outside of the xampp/htdocs actually. Then, I set the root of my PHP project to this theme source folder, and then using the Project Properties -> Include Path facility to allow NetBeans to include the WordPress folder, it will appear under Include Path in Project Explorer, enabling 'IntelliSense' etc. This way you can start a new NetBeans project per plugin/theme, basically, just including the WordPress core in each. Furthermore, I have NetBeans set up to copy the source files to the xampp\htdocs\mysite2\wp-content\themes\ folder on save and project load (set up in preferences). Here's a pic: NetBeans WordPress Setup
The best way I've found so far is to use a hardlink.
If I keep the files in Netbeans' project directory everything works. But Wordpress sometimes does not recognize that the theme is there. I.e. in some wp-admin menu's. But I'm able to display a Theme just fine.
I create the project as a php project in Netbeans.
Then link my (pubic html) folder from the Netbeans directory.
mklink /J C:\LinkToFolder C:\Users\Name\OriginalFolder
Use " quotes if your path has spaces
I use:
mklink /J "C:\xampp\htdocs\wptheme\wp-content\themes\themename"
"C:\Users\Probook 1\Documents\NetBeansProjects\projectname\public_html"
Then I setup the netbeans project to load an external page when I run the project. (See File => Project Properties=>Run Configuration)
I'll be looking into doing the same with plugins soon. Practically I can't see a reason this won't work for plugins too.
I want to try and see if Netbeans copes with the hardlink better than Apache does. (I.e. if I setup the project first then move the files to Xampp and create a hardlink in Netbeans' project directory. I.e. Projectname\public_html
(If anyone does it first let me know how it goes)
It's more important to me that Netbeans can backup and function. As long as I can display what I'm developing realtime.
AFAIK Netbeans can intergrate with Xampp to run it's debugging (Xdebug)