Every time I publish, I am having to remember to check that the Assets folder in my DevPack has been published, if I have changed any assets (PHP includes in my case). I end up having to copy the files from my DevPack to the local published to site. Even a Publish All doesn’t work.
When publishing to a local site happens, it is over in less than 3 seconds (Mac mini M4 Pro). Is there a log produced by Elements of the list of files published, so it can be checked?
I am making this a separate thread, just to make it easier to comment on this issue as it probably got lost in the other thread?
May be related to some of the shipped form issues you’re encountering.
The first and only time I tried the shipped form. I quickly realised that the files in the backend, from memory: rw > elements > email, where not being published, at least not consistently. Which led to a 404 in the console when testing the form.
I could see no rhyme or reason in what triggered them to be published, but one minute a republish all files was like 60 files for example, then randomly a publish would be like 680 files (I assume thats when it decided to publish the email backend).
As you will be revamping Publishing, it would be useful to be able to right-click on the Elements icon in the dock and click Publish to repeat the last publish. Maybe, the presence (or not) of a publish dock menu item to be set in settings.
I remember one of your videos or comments in my distant mind that said something about Chillidog, as I have used them for years and Greg and team are brilliant is there something in the works bout publishing and Chillidog?
The issue I raised in post one of this thread is much more basic than working with a reliable host.
At the moment, I am just publishing (or not ) to local files to be used with Mamp Pro / ServBay. The issue is that Elements isn’t recognising that some files have changed and isn’t publishing them to the local folders. Even a “Publish All” is working in “Publish Some” mode.
It make testing a bit of a frustrating experience.
The issue is understood by @dan and team and it is on their list to fix. I was just flagging it up as I am hoping it will be sooner rather than later.
Just a bit more input on this. It seems like that if you first launch Elements and do a publish, all of the files in the shared > assets folder are published, regardless as to whether you changed them or not.
If, still within the same Elements session, you make any changes to any of the files in the shared > assets folder and then do a publish, these changed files aren’t published.
I was trying to train myself (and failing ) to remember to do a manual copy after a publish if I had altered any of these files.
I have now found that the quickest way is to close down Elements and then restart it, open the project and then do a publish and all is good.
Thought this info might help with the problem resolution?
Yes, I’ve noticed this too. But don’t worry, although Publishing is a little wonky at the moment, it is high on the list to fix up and resolve these outstanding issues. Hang in there!
) to local files to be used with Mamp Pro / ServBay. The issue is that Elements isn’t recognising that some files have changed and isn’t publishing them to the local folders. Even a “Publish All” is working in “Publish Some” mode. 