I am testing a sub-domain on my local ServBay setup.
Accepting I could be doing something wrong, I have the following issue.
I have added a folder ‘subdomain’ to the root of my website (website.com). I have configured a new web server at new.website.com and set the root folder to be the folder ‘subdomain’.
I have configured a new publishing destination in Elements using the above details.
I have then done a publish all to the new destination.
On the first attempt, while the publishing was in progress, I got a kernel panic attack and my Mac mini rebooted!
It hasn’t happened since.
However not all the files in the rw folder in the subdomain are being published?
This is the structure of the rw folder at the main website root level:
The folders com.logrunner.blog and com.realmac.apipack are missing?
I was doing a Publish All as even with the new publishing (1.0.8) system, if you make changes to code in the shared area, it doesn’t appear to publish the changed shared code?
I am attempting to test this out prior to do doing it for real on my production site.
btw. We are working on another update to Elements with better publican diagnostics as we’re determined to ensure we can solve ALL publishing issues FAST! Stay tuned for that.
OK, so I backed up my ‘published to’ folder.
I then deleted everything in the ‘published to’ folder (main-domain and sub-domain).
I quit and restarted Elements.
I then did a Publish All for the main-domain..
Looking at the results, I can see that the issue now also manifests itself in the main-domain. Everything was published (AFAICS) except the two folders as previously noted: com.logrunner.blog and com.realmac.apipack which are missing and haven’t been published?
The website doesn’t work without these folders. Obviously, for the moment, I can recover them from the backup, so it isn’t a show-stopper, just a small inconvenience.
So, I don’t think the issue is related to the sub-domain and I only noticed it because the sub-domain was a new setup.
The API pack has now been merged into the Core pack, so that’s fine. Your blog pack should only be deployed if it’s being used in the project. Can you confirm that it’s in use and should contain files?
