Is it OK to have a Rapid Weaver Classic | Stacks | Foundry 3 website and then add a single Elements page to the website named e.g. elements.php.
Is there any conflict with file / folder naming between Rapid Weaver Classic and Elements that might cause problems if there are two separate publishing actions on the same website?
I don’t think so, especially if you are publishing to a sub folder.
You can always export first and upload manually to check.
Let me know how you get on,
@dan I changed the home page filename from index.php to calendar.php and when I go to to the website I am getting a 500 error (both locally on MAMP and remotely).
I had deleted the index related files i.e. index.php | .css | .js before publishing the new files with names calendar.php | .css | .js.
There was one conflict I picked up which was the sitemap.xml which I just skipped. I am going to reinstate the home page using index.php and put the calendar code into another page and then just upload that and see what happens.
I know you are looking at the publishing section but I couldn’t get the Publishing credentials correct for the remote site (it failed the Test button) but this works OK with rapid Weaver Classic which appears to have more customisable options than Elements.
I am copying files using Forklift to update the remote site.