What phil meant with "much too early to ask" he meant something like "not this year".

to complain about improvement (which was requested more than once) sounds strange to me.

tbh i feel sorry for all the people that worked hard on addons, for e.g. the Cup Addon V5 took couple of months and Listener Hosting Addon, Eggyz Shop Addon all took alot of time to bad it will not be compatibly with the new version of webspell furthermore would be nice if you could post a news and keep the Community updated like a rough estimate when it will be released and what have u changed etc...

much to early to ask. but we will try to make it possible to update.

maybe early to ask, but is it going to be possible to update to this new version from the current ones? or is that lack of compatibility not going to allow updates, fresh installs only?

it is done when it is done.

This is intresting, do you have a rough estimation when it will be released?

as i said, we are completey rewriting webspell from scratch. the new code is ofc not compatible in any way to the old code.

I'm sorry for that. So, why don't you upload a temporary set of patches?

the current webspell code is based on a codebase which is older then 7 years, there are a lot of ugly issues in there. that's why we are currently completely rewriting webspell for the webspell5 release. the issues you are mentioning allready have been addressed.

- Move any file that should be included and must not called directly from the browser in a different folder (es. addons?)
- add an .htaccess with deny from all in the folders where there's no need to access via browser

---.htaccess---

----------------

- use a define to check if the calling file can include the addon file

ex.
add in
index.php and admin/admincenter.php



and at the beginning of the called files (ex. those within the addons folder)



This is just a well know common practice.


- There's no need to leave the template within the index.php just add something to select a different template within a template folder

just a common include in the index.php can solve the problem by calling the needed template and the selection of the template can be automated by using a variable from the _settings.php file or from the database.


Those modifications are very simple and mandatory (imo).