Ajax AutoComplete Support Product Page
Answered
promised upgrades from 4-5 years ago never occurred.
Asked 19 Jun 2019 12:45:06
1
has this question
19 Jun 2019 12:45:06 Web Master posted:
Then why has there been no update for those who purchased this extension and are using current versions of php. They have effectively lost their money since promised upgrades from 4-5 years ago never occurred.
Official Answer
Replied 19 Jun 2019 15:24:01
You either don't understand what i am saying or are trying to make fun of this.
How can we fix something, which is no longer supported in DW (talking about server behaviors dropped by Adobe)? This extension is based on them, so there is no way to "fix" this, as we cannot go and fix the server behaviors code, which is producing the errors in PHP 5.6+ (and not our extension .... ).
This topic has been discussed with you more than a couple of times and you just refuse to accept that the errors caused on the pages with PHP 5.6+ are caused only by DW server behaviors code. And that's nothing related to our tools or us.
Also, i see that you've been using this extension quite well on your renuionmanager site:
Currently a new autocomplete tool for Dreamweaver is not in our top priority list.
As for Wappler, of course we don't expect all of the DMXzone users to "get involved". Wappler community already passed 5000 users and it keeps growing. The ideas shared there are really nice and give us some really nice feedback so we will continue developing it as it is now - community driven.
How can we fix something, which is no longer supported in DW (talking about server behaviors dropped by Adobe)? This extension is based on them, so there is no way to "fix" this, as we cannot go and fix the server behaviors code, which is producing the errors in PHP 5.6+ (and not our extension .... ).
This topic has been discussed with you more than a couple of times and you just refuse to accept that the errors caused on the pages with PHP 5.6+ are caused only by DW server behaviors code. And that's nothing related to our tools or us.
Also, i see that you've been using this extension quite well on your renuionmanager site:
Currently a new autocomplete tool for Dreamweaver is not in our top priority list.
As for Wappler, of course we don't expect all of the DMXzone users to "get involved". Wappler community already passed 5000 users and it keeps growing. The ideas shared there are really nice and give us some really nice feedback so we will continue developing it as it is now - community driven.
Replies
Replied 19 Jun 2019 15:07:09
19 Jun 2019 15:07:09 Teodor Kuduschiev replied:
This extension relies on Dreamweaver Server Behaviors, which have been discontinued years ago.
You can ask Adobe, why they never updated their Server Behaviors, as this extension does not work without them.
You can ask Adobe, why they never updated their Server Behaviors, as this extension does not work without them.
Replied 19 Jun 2019 15:11:50
19 Jun 2019 15:11:50 Web Master replied:
No I asked why DMX has not updated this extension as it stated in would 4 years ago. if there is no intention of updating the extension then how can I get a refund on my purchase for something is is basically worthless at this time and has been for the last 4 years.
Replied 19 Jun 2019 15:13:11
19 Jun 2019 15:13:11 Teodor Kuduschiev replied:
There is no way for us to fix Adobe Server Behaviors code, which our extension relies on to function.
You cannot get a refund for a product purchased 4! years ago ...
You cannot get a refund for a product purchased 4! years ago ...
Replied 19 Jun 2019 15:16:08
19 Jun 2019 15:16:08 Web Master replied:
Then fix your extension so it will work. And if you can't or don't know how to then yes I want a refund because this product has been unusable for 4 years now. You wonder why some won't get involved with Wappler - this is the reason
Replied 19 Jun 2019 15:24:01
19 Jun 2019 15:24:01 Teodor Kuduschiev replied:
You either don't understand what i am saying or are trying to make fun of this.
How can we fix something, which is no longer supported in DW (talking about server behaviors dropped by Adobe)? This extension is based on them, so there is no way to "fix" this, as we cannot go and fix the server behaviors code, which is producing the errors in PHP 5.6+ (and not our extension .... ).
This topic has been discussed with you more than a couple of times and you just refuse to accept that the errors caused on the pages with PHP 5.6+ are caused only by DW server behaviors code. And that's nothing related to our tools or us.
Also, i see that you've been using this extension quite well on your renuionmanager site:
Currently a new autocomplete tool for Dreamweaver is not in our top priority list.
As for Wappler, of course we don't expect all of the DMXzone users to "get involved". Wappler community already passed 5000 users and it keeps growing. The ideas shared there are really nice and give us some really nice feedback so we will continue developing it as it is now - community driven.
How can we fix something, which is no longer supported in DW (talking about server behaviors dropped by Adobe)? This extension is based on them, so there is no way to "fix" this, as we cannot go and fix the server behaviors code, which is producing the errors in PHP 5.6+ (and not our extension .... ).
This topic has been discussed with you more than a couple of times and you just refuse to accept that the errors caused on the pages with PHP 5.6+ are caused only by DW server behaviors code. And that's nothing related to our tools or us.
Also, i see that you've been using this extension quite well on your renuionmanager site:
Currently a new autocomplete tool for Dreamweaver is not in our top priority list.
As for Wappler, of course we don't expect all of the DMXzone users to "get involved". Wappler community already passed 5000 users and it keeps growing. The ideas shared there are really nice and give us some really nice feedback so we will continue developing it as it is now - community driven.