Sitebuilder Unaccessable on port:2006 after Plesk CP install...
thank you for writing back...
>One Button ‘Edit in SiteBuilder’ in Plesk Panel
>No more own Business Logic in Sitebuilder. Now it’s just a library to edit sites.
>No more standalone SiteBuilder product (will be available later).
Do you know when this will be available?
>No more separate license key for SiteBuilder in Plesk. Licensing is performed via Plesk main key (SiteBuilder sites >property)
>Right now there is no migration path for old SiteBuilder sites.
Do you know if there will ever be any type of migration tool for 4.x to 5.x Sitebuilder?
>Old sites are available after upgrade as custom buttons.
I'm not concerned with the buttons. All our customers are used to accessing their sites on port:2006
They cannot do this anymore. It won't even direct them to legacy Sitebuilder 4.x.
I'm also concerned that there are no modules in new Sitebuilder 5.x.
Since Sitebuilder legacy does not function on port:2006 some of our users cannot get into their sites for managing.
Since Sitebuilder 5.x does not contain any modules that are the same as in Sitebuilder 4.x such as Forum, Blog, Image Gallery, Registration, etc. they cannot build their sites even manually. They now cannot access their sites through legacy Sitebuilder. Our customers are very mad at us that we did this. They now cannot manage their sites.
We're going to be forced to go back to Plesk 9.x within a few days. We've had Plsk 10.x running for about 2 - 3 weeks now with so many angry customers they're either going to leave us or we have to put things back the way it was. Please understand that they use the online Sitebuilder to build their sites easily. Sitebuilder 4.x was simple and did it's job except they needed to be able to create sites with more than 1 layer deep and be able to store data in the modules, logically, physically.
Is there any way to get the image gallery pictures out of Sitebuilder 4.x as the original files that they would have uploaded? Is there any directory in /httpdocs/etc that contains the actual files they would have uploaded into an Image Gallery Module for them to be able to use an API module to take the place of the Sitebuilder 4.x image gallery?
I've been struggling to find work-arounds but there are none.
Your company has really done a good one this time. Given us a product that goes no where... It keeps on getting worse and worse. When you were SWSoft your company thought of us as customers. Now we're just users that you don't seem to care about...