Wappler and its evolution: let's not forget the basics

Wappler General
, , , ,
1

Version: All
System: Windows 10
Server: Wamp, MAMP PRO, Wappler local server: Apache, PHP 8.3.xxx, Mysql,

I have been using Wappler for some time because I am not satisfied with other development environments.
I often need to go quickly in the graphical structure (Frontend and Backend). Even if I am used to coding, using a Low-code tool saves a lot of time. But the time saved is quickly lost because of minor bugs that should no longer exist today.
The development team has done a great job and Wappler is still great. However, I lose a lot of time when some basic functions no longer work.
The beta versions expose even more what was wrong in normal times. Unfortunately, the updates go in the direction of the evolution of technologies and new requests by forgetting the basics of standard use:

  • Copy-paste or duplicate with the mouse (App Structure)
  • Drag-and-drop does not exist in the graphical editor (Design), which is not so serious, but remains problematic in the AppStructure window.
  • Routing that no longer works: This happens often. And this exposes the general problem that I raise today.
  • Many other small errors...

Indeed, the direction taken by the development team goes towards the modularity and flexibility of new innovations (NodeJS). But you forget that the web still works with PHP servers. It's the basis.

For example, there is not only Docker in life. Developers' mistakes are often to use large configurations while the end user is quite the opposite (graphic software, video games, etc.).

In web development, even if the servers have enormous capacities, there is always a majority that works with interfaces consuming few resources.

  • Linux, PHP, MySql, HTML, Javascript... even if we can add the latest innovations, the bases remain.

I am a French-speaking Pro user who cannot complete personal projects that should use the full power of Wappler. And especially promote it. I would like to create a team but I can't include this environment that would give us a breath of fresh air. I often have to restart projects when dynamic programming doesn't work anymore under Wappler.

I just ask you not to forget PHP users.

I continue to use this environment and make my modest contribution to the community. I persevere because I believe in this tool.

Thank you

2 Likes
2

PHP server side includes. :slight_smile:

3

Hi Juan,

I am curious what problems are you having with PHP includes? Maybe start a new thread on that? I have been using PHP includes for years in Wappler without an issue.

4

Not the include like PHP inlcude function.

Like this:

<?php
if ($x == 0)   { ?>

    // Your code here

<?php
}
?>

I this this is Server Side Inlcudes right? SSI?

5

If you put that code inside a section element, you should be able to easily select it and convert it to an SSI.

Problem with what you are trying to do is there is no way to select php tags in the app structure.

My apologies to the original poster for hijacking this thread. I too hope they don't forget about PHP.

1 Like
6

Beware of PHP tags. Like any programming language and their environment, there are rules.
Programming in an environment is not programming as if you wanted to create a plugin in a software with hooks at all levels.
Being a fervent user of Wordpress, for example, I can no longer stand these incessant calls with the opening and closing of PHP tags... but we have no choice.
For Wappler, I agree with the SSI rules. This avoids bugs and unnecessarily weighing down the source code.
With the long-awaited arrival of custom extensions, this risked creating even more constraints.

1 Like
7

Server connect and App connect extensions have been with us quite a long time now. I use them all the time

2 Likes