Hi,
Jooglar wrote:Thank God it's working 
WE BOTH DESERVE A BEER!!!
Anyway, the SQL Injection is not an easy duty for a hacker because he'd need first the db. settings and that'd be something really hard to find!
BEER, oh yes! I have never said no!! I would love it!!!
Atleast if it is possible to structure and place the query.txt as well as the wrapperMySQL.php in the directory of administrators of the remote, then atleast I can protect the administrator directory and remove the .htaccess while publishing/sending the content and have .htaccess effective in a Normal condition.
Currently this is not possible.
Since you do not have your own server, you do not realise how and whats going on. There are thousands f scripts that simply scans many servers for vulnerability and I see it daily those calls by script robots.
Hence I need to have a solution for the protection.
If you do not have the time of modification and placing it into a com_multip directory of remote, then what I will do is as follows:
1) I will delete the query.txt + wrapperMySQL.php after sending the content.
2) Use the Checksite funtion that will generate the wrapperMySQL.php in the remote installation.
So may be one anathor option is always to delete the wrapperMySQL.php after sending the content from the remote. Why hould it stay there and wait for those shitty Robot scripts?
Again and again: Thanking you for your help.
I will open a new thread with a new wish/feature request. Now I know how your script works and it is easier to make a new wish list as compared to others. I wish I had the source code so that i would help you in developing the component as well.