geoff3
posted this
18 November 2019
I have noticed that PHP is broken in HTML exports.
Example:
if ($mysqli->connect_errno) {
echo "An error occurred: " . $mysqli->connect_error . "";
exit;
}
is exported as:
if ($mysqli->connect_errno) {
echo "An error occurred: " . $mysqli->connect_error . "";
exit;
}
So simply renaming the exported file name to a .php file is not going to work even though it would make Nicepage a lot more developer-friendly if it did.
I understand the approach to having the php function in cms templates, so you can make extra MySQL query calls and alike but it is also sensible to support independent exports of files that function correctly. Not everybody uses WordPress or Joomla on every website, actually, those applications can be bloatware and introduce unnecessary maintenance and security problems in situations when you only need a few simple PHP pages to read and display data from a database CRUD system.
I have noticed that PHP is broken in HTML exports.
Example:
if ($mysqli->connect_errno) {
echo "An error occurred: " . $mysqli->connect_error . "";
exit;
}
is exported as:
if ($mysqli->connect_errno) {
echo "An error occurred: " . $mysqli->connect_error . "";
exit;
}
So simply renaming the exported file name to a .php file is not going to work even though it would make Nicepage a lot more developer-friendly if it did.
I understand the approach to having the php function in cms templates, so you can make extra MySQL query calls and alike but it is also sensible to support independent exports of files that function correctly. Not everybody uses WordPress or Joomla on every website, actually, those applications can be bloatware and introduce unnecessary maintenance and security problems in situations when you only need a few simple PHP pages to read and display data from a database CRUD system.