from execlp's documentation:
The functions execlp and execvp will duplicate the actions of the shell in searching for an executable file if the specified file name does not contain a slash (/) character. The search path is the path specified in the environment by the PATH variable. If this variable isn't specified, the default path ``:/bin:/usr/bin'' is used. In addition, certain errors are treated specially.
And now, this is how amuled tries to start the webserver:
amule.cpp:831: execlp("amuleweb", "amuleweb", (const char *)unicode2char(wxT("--amule-config-file=") + aMuleConfigFile), 0);
Therefore, if amuleweb is not in the PATH, amuled won't be able to run it, even when they're in the same directory. About getting a second (defunct) amuled instead of amuleweb, read the documentation on fork(2) and exec(3).
About your bugs concerning statistics: They are definiately not related to amuleweb nor EC. The statistics tree is simply copied from the core as text -- no way to mess with it. It might be realted to amule daemon, if at all they are really bugs.
Log and debug log: aMule has only one log -- it doesn't matter how we call it. The bug is actually in the webserver template, which was originally imported from eMule. I'll remove the 'Debug Log' item.
Serverlist: it's rather an amuled issue, not amuleweb's. Anyways, I don't have it here.
Progress bar images: I have two machines, it works on one, and doesn't on the other. Funny, isn't it?
Hoping to be helpful,
GonoszTopi