Hi, I am a new customer (I have recently been training on the beta) and I am impatiently waiting for the release of Xway.
I need a contact form and a blog on my sites. Can you advise me on the options with Xway?
Likewise and last question, will I be able to integrate snippets to use php scripts and integrate my reservation calendar in php on a page?
Some contact form and blog suggestions:
- Hosting your own contact form has become problematic with anti-spam measures, but you can use an online form generator (see Spam Free Contact Form and Creating a Contact form). Alternatively, you can use a mailto link (Xway 1.0 has improved support for mailto links).
- Blog: you could do this in Xway (e.g. News page in the Xway tutorial), but I would suggest using a blog site (e.g. Blogger) and linking to that from your website.
Iām not sure what is involved with snippets, but you can add HTML code via markup items.
You can add PHP using the Generic Markup section of the Page Inspector.
1 Like
Iām thinking about pieces of code to integrate directly either in the āheadā or ābodyā part of the HTML page. Iām asking this question to find out if itās possible in order to avoid having to input them directly on the published page and therefore having to re-enter them every time a modification is made under Xway on the page in question. Sorry for this question, Iām a complete beginner with Xway (I do have experience with Dreamweaver, yes, it still existsš±ā¦ RapidWeaver, though weāre not really sure about it at the momentš¬, and āthe hard wayā with TextEdit, Emacs (the Linux versionš§), and VSCode).
ADD : I told you Iām a Totally Newbie. Iāve just found Markup things. Great 
Hi Bruno,
You can add code via the Generic Markup, JavaScript Markup, and CSS Markup sections in the Page Inspector. Plus (as youāve discovered) markup items can be placed anywhere on a page.
1 Like
Hi Jeremy,
todayās dummy question: does xway handle .php extensions for pages? I tried to configure Sitelok from Vibralogix with the beta but it doesnāt work (renaming .html .php before exporting pages). Maybe an export issue while publishing is not enabled?
You should be able to give pages a .php extension by renaming them in the File Name field near the top of the Page Inspector.
Yes thatās what Iāve done. And I put snippets of code ābefore htmlā in generic markup. Iāll try again later with dev console and let you know the results. Thanks for your answer.
Have you uploaded your site to a server?
PHP is a server-scripting language, so it wonāt work if youāre previewing locally.
I use Mampro. When I give the .php extension to the pages of the site, only index.php is displayed in a browser, the other pages (built from the getting started manual) are not displayed, only a blue gray background. I do this test only by modifying the extension of the page, I have not yet modified the markup with the code from Sitelok.
For sitelok, I discovered the reason for its lack of functioning: each time I export the site to its directory it overwrites everything that is there, so the Sitelok files directory (slpw) disappears, which is annoying to make it work 
. The problem is that I can only recover the Sitelok code snippet after installing it in the root of my site and when I export the site again, it overwrites everything, no more sitelok directory 
sorry to start boring you right from the betaā¦ imagine when Iāll be warmed up for the release of version 1.0 
Mampro is a local server running under macOS?
I think that what you need to do is have a folder that is separate from Xwayās Export folder, and put your sitelok folder here. Then when you have exported from Xway, copy the files from the Export folder (Select All, then copy) and paste them into the folder that contains your sitelok folder (replacing any files that you have previously copied).
Export synchronises a documentās internal Site folder with an external folder. It doesnāt know about any additional content (e.g. sitelok folder).
Yes Mampro is a ālampā for mac (or windows). Thanks for the tip with two folder. I have no clue about the .php issue, dev console doesnāt show any trouble. Really weird. I use Mampro for other php site tests : it works well. I donāt think itās a Mampro issue. When I put back the .html to pages all works well again without any other change.
Can you give us some more information about what is happening with the PHP pages? They seem to publish OK for me.
I am running macos sequoia on a mac m2 ultra, mampro version 6 up to date, php 8 support (8.2 from memory, I am no longer in front of my mac at the moment). I created the site following the manual (which is very well done). Everything works perfectly in html. In the inspector, I change index.html to index.php (homepage) then news.html to news.php, etc. I export the site and only the index.php page is displayed correctly. The other pages (whether I call them from the navigation menu or with the full url in the Safari browser) are not displayed, only the gray blue background. If I put the html extension back in place and export the site again, everything works fine again.
ADD : I think this is not enough information to allow you to intervene effectively. I do not have the possibility to do better today, tomorrow I will build a new test site (a very simple one, three pages .php) with Xway and see what it gives. I will have time to test it also online on my test server. Thank you for your support, I will keep you informed tomorrow.
I havenāt used mampro, but I have run hundreds of different PHP servers over the years, and one thing you have to take care of in the configuration of the Apache server is to ensure that your default (index.html) settings also include index.php. You can actually configure it to serve literally any filename, any extension as the index page, so donāt feel limited to that naming convention.
The config line is DirectoryIndex, and it needs to be inside the <Directory /path/to/site/root> block somewhere, along with the Options Indexes line:
DirectoryIndex landing.html index.html index.php whatever.xyz
You can have multiple values for this configuration, and Apache will try them until it hits a match. I believe they are considered left to right in the space-delimited list.
Walter
1 Like
@waltd Thank you for the tip about extension and apache.
@Jeremy Found it! Safariās cache (since the Sequoia update) is a horror. Although I always empty it between two tests (and several times during the same test), it continues to keep traces of what should no longer be there, in this case it looks for html when there is none left, ditto for php when I modify. I have to go through another browser until Mr. Safari stops doing anything. I took advantage of Waltdās suggestion to check if the new version of Mampro (7) had not forgotten the extensions, yes, when you have other .php pages at the root of the site it was not indicated.
In short, thatās it: Vibralogixās Sitelok works perfectly with Xway and Xway works perfectly with PHP extensions. The problem was caused by Safariās cache.
I find that what is happening with Safari and its cache management is a bit strange, am I the only one in this case?
ADD : nothing appears in dev console, so impossible to find it this way
Iām not on Sequoia yet, but perhaps Reload Page from Origin would help?
Thanks for the tip. Yes itās ācleanerā but still some problems. I followed a friendās recommendations and switched to Chrome, it works much better with the dev console, I no longer have any cache issues (Iām keeping my fingers crossed anyway 
).
Do you plan to release a complete manual on all the features of Xway (documentation on the inspector and its tools for example 
). I am starting to ābuildā a blog (markdown articles āretrieved and transformedā into html to display the list and articles) and that would allow me to go a little faster in my āappropriationā of Xway. In the same spirit I think of āmakingā a contact form linked to my sql database and ābuildingā some effects like parallax, animationsā¦ Iāve already said that but Iām very enthusiastic about Xway and all its potential. Itās a great job 
Canāt wait to purchase v1.0 Iām still pressing the pedestrian call button 
There is a detailed reference manual which you can view by choosing Xway User Guide from the Help menu (in Xway).
1 Like