ME

Below are a few rewrites added to a local `.htaccess` within the Element Call root folder that seems to work for me. Maybe one should add this or something similar...

@AndrewFerr Will you file a PR accordingly?

IMHO, this could be easily handled within the app itself (i.e. outside of LLPhant) via a (sub) system message stack.

The last version that works properly for me is `v1.47.15538 (pre-release)`. When switching from that version to `v1.47.15561 (pre-release)` I get a huge number of issues (712 compared to 5...

It is located within a subfolder inside the root `C:\xampp\htdocs` referenced via a class map similar to the composer autoload class map.

> so it is in `C:\xampp\htdocs\...` and in VSCode, you open the folder `C:\xampp\htdocs\` ? That's right. (There must have been a change from `v1.47.15538 (pre-release)` to `v1.47.15561 (pre-release)` that...

> Is there anything special in the path? A non-ascii character maybe? No, nothing special. No special characters etc. This is not the only affected class. The number of affected...

The entries in this class map looks like, e.g. ... `'phpseclib3\\Crypt\\AES' => 'phpseclib/phpseclib/phpseclib/Crypt/AES.php',` ... whereas the absolute (full) path is built inside a "spl_autoload_register", In this case '`c:/xampp/htdocs/' . LIBRARYROOT...

That's right. To be completely correct, the path would be '`c:\xampp\htdocs\lib\`phpseclib/phpseclib/phpseclib/Crypt/AES.php', as the path to the root directory of the library is created taking the DIRECTORY_SEPARATOR into account. Replacing the...

Ok. I would just like to add that if I copy the issue and not just the issue message, the following data is given as an example with respect to...