Pure ASP Upload 3 Support Product Page

Trying to use Pure ASP Upload 3.15

Asked 11 Jan 2019 14:30:38
has this question
11 Jan 2019 14:30:38 Tim Pollard posted:
I need to move a legacy site from a dying server and the site was built using Pure ASP Upload 3.14. The pages won't run on the new server and give me the ADO 2.5 required error. I see that 3.15 should solve this but I am still using CS5.5 Dreamweaver. So your extension manager won't install it because I think it needs CS6 to function and the direct download will only give me a .zxp which CS5.5 can't use, so I am stuck. The only newer versions of Dreamweaver I could get won't work with any of this stuff now they have dropped support for database coding. Clearly in the long term I need to start again with a complete rebuild of the site using newer methods, but in the short term I need to get my site operating again. Can you help please?


Replied 11 Jan 2019 14:33:20
11 Jan 2019 14:33:20 Teodor Kuduschiev replied:
What do you mean by
QuoteSo your extension manager won't install it because I think it needs CS6 to function
? Our extension manager works fine with all DW versions from 8 to CC2019...
Replied 11 Jan 2019 15:27:55
11 Jan 2019 15:27:55 Tim Pollard replied:
Hi Teodor
Thanks for the reply.
I downloaded your extension manager and ran the installer, and I have PASP3.1.5 downloaded to it. Now when I open your Ext Mgr it it says Extension Manager, Pure ASP Upload 3 requires a minimum Dreamweaver version of 12. Install Anyway?. If I click OK it shows me the activity indicator and says it has done it, but when I open CS5.5 Extension Manager it is still showing 3.1.4 and telling me there is an update available. When I open DW I would expect the extension installation routine to start and try to activate, but it doesn't. And when I apply the extension to a page it is still using the old one.
Replied 11 Jan 2019 15:37:20
11 Jan 2019 15:37:20 Teodor Kuduschiev replied:
Well you either use Adobe EM or DMXzone EM.
You won't see any change in Adobe EM after using DMXZone EM ....

If DMXzone EM installs it and shows version 3.1.5 as installed then it is installed. When installing extensions using DMXzone EM you won't see any "Installation dialogs" in DW anymore, they are no longer required and we are not using them.
Make sure to delete the old asp upload file file locally and re-apply it on a page, this will generate the new file which you need to upload to your server ....
Replied 11 Jan 2019 15:47:42
11 Jan 2019 15:47:42 Tim Pollard replied:
It doesn't seem to be installed! Your EM says it is, but even if I remove PASP from a page and reinstall it, I get the old version.
Replied 11 Jan 2019 15:51:10
11 Jan 2019 15:51:10 Tim Pollard replied:
And if I make a new page and apply PASP I get the old one.
Replied 11 Jan 2019 15:52:25
11 Jan 2019 15:52:25 Teodor Kuduschiev replied:
If the extension manger shows it as installed, then it surely is

Which file are you looking at exactly? And are you sure you deleted the old one before re-applying it?
Replied 11 Jan 2019 15:55:38
11 Jan 2019 15:55:38 Tim Pollard replied:
I tried using AEM to remove the old one and then your EM to reinstall the new one.

Apply to a new page and the old one is still there!

Is there a way to manually uninstall the older one, please?
Replied 11 Jan 2019 16:01:45
11 Jan 2019 16:01:45 Tim Pollard replied:
I also tried updating SIP, your EM says the version is now 2.5.8, but when applied in DW the code shows it as being 2.5.7
Replied 12 Jan 2019 10:41:04
12 Jan 2019 10:41:04 Teodor Kuduschiev replied:
Which files are you checking exactly, that say it's an older version?
Replied 14 Jan 2019 06:59:02
14 Jan 2019 06:59:02 Tim Pollard replied:
What they write in the code on a page they have been applied to and what it says in the .js file they install to the user data area where extensions are stored. I have totally removed them from both the DMX EM and Adobe EM, checked they are fully gone from the place they are installed to, then reinstalled using DMX EM and they still claim to be PU 3.1.3 and SIP 2.5.6

So I think you are right, they are installing but the team that compiled the extensions didn't update the version number in the installed code and they are claiming to be older versions than they actually are.

Reply to this topic