SCRIPTCASE - Update 9.8 part two

[gomi]

That was always working is the license registration.
THE ONLY PART OF THIS SHIT.

First install and restore - no app.
Import the app - no no - app ist still available.

Second Install - delete all
First Question License!!!

I’m sorry but you guys are so inept - it sucks.
It’s rude that you’re asking for money for it…

MISTAKE
Even the registration doesn’t work.
You guys are so incompetent, it’s a scandal.

[iosson]

It is not very constructive and hardly motivating to the people trying to develop this and make it work.

Yes, SC is often buggy and frustrating, but abusing people is not the way to get the most out of them.

As we’ve always seen initial releases are for the adventurous, but fairly quickly most problems are ironed out.

I’m sure this represents a lot of work at their end, but they remain invested in developing and progressing the environment.

[ken]

I agree…name calling and constantly abusing is not helpful.
Instead layout the problems…bring it to SC’s notice. OP needs to understand that.
I want SC 9.8 with PHP 8.x to work seamlessly as much as anybody else but I am not going to get in the gutter when reporting issues.

[aducom]

Ranting is not productive for sure. I am an old SC user since version 5 and each and every time that a new version comes out it is the same old story of bugs, more bugs and finally a version that works. I disagree with iosson, that fairly quickly issues are ironed out. I have examples of months. Time, that we do not have as PHP 7.3 is already end-of-life. I can understand that this is a beta, but actually it isn’t. For me a beta is nearly production ready, perhaps some glitches. But here it looks (again) that SC does not test well and leave it to the public as a ‘beta’. Also I don’t understand it - at all - why these issues occur. If they would focus on the incompatibilities between 7.3 and 8.1 then surely there would not be these issues. PHP 8.x is a must and even if SC ran under 7.3, they should be able to generate 8.x code. After all, they show the migration issues in their own webinars. In the current situation it is hard to determine if the issues are in your own custom code, the generator or the libs. It is a free choice to decide when to migrate, but PHP 8.1 is advertised here in the header as a premium version, not a beta.
Suppose if you deliver your software this way to your customers? Mine would be furious, reason why I personally abandoned and replaced SC. Business-wise (I’m a teamlead of a dev team at the university of Groningen) I am still depending on it and I need a working 8.1 version, and fast…

[gomi]

No one was called names.
That is the truth. And if you like to do everything three times for expensive money… Do that.

[gomi]

Thank you for your comment.
Completely uninteresting.

[maximnl]

yet SC 9.7 is advertised as fully compatible with php8, they literally say you can run older versions of SC on php8. I do not get all this php8 buzz, it seems that php8 canceled curly braces for arrays, but this is more or les all. who is using curly braces for arrays anyway?
for me, i have no urgency to move to php8, most hostings will support php 8-. php8 looks attractive: huge performance gains, perhaps a better security, which is a huge problem. all in all hoping sc 9.9 will be stable, and we still get 20 days to test for free. Unfortunately paying for it with our own time, which very quickly exceeds the licencing costs, basically in one/half a day of testing SC should realise that and perhaps adjust some priorities.

[aducom]

PHP 7.4 was never supported officially, and it took some measures to make the applications work under PHP 7.4. Because the syntax differences are limited (but a bit more complex than you put it), I can’t see why this version has so many issues. The main reason for the ‘fuzz’ of PHP is that in these times of increasing security and awareness, companies/institutes (like my Uni) refuse to run applications build with end-of-life PHP version. PHP 7.3 is over 8 months eol, PHP 7.4 will be next december. I have to have migrated all our applications to PHP 8.1 by then, or we are in serious trouble with our security department. As it is nearly Q4, this is becoming a severe issue, not only to me, but to many of us. Especially when SC fails to focus on the importance of this and still add whisles and bells.

[maximnl]

end of life does not mean it is less secure than in Q3 , security just seems to be a cash cow for ICT to pull money from the business and fix bugs without explaining what happened.
i guess you get nice conversations with ict in the near future , good luck with the migration !

[aducom]

Thank you

(Discussions with security officers are always interesting. But even professionally, PHP is developing fast, and Scriptcase needs to step up or fail).

[ken]

The intent was not to make a interesting comment to you. But to imply to you to refrain from using curse words on the forum. Keep it decent.

[gomi]

Sorry, you have problems understanding language.
Let it stay. I’m not interested in your pointless chatter.
Go play in the yard.

[jlboutin60]

I am for sure not a big fan of Scriptcase bug issues, lack of support, worthless paid support, etc…

But for sure I am not at all a fan of members who only use the forum to complain and not to share knowledge with the others.

You can bash on me now, I am ready

[aducom]

Guys, stop this. I’ve been in a situation where I was nearly as far as Gomi, completely desperate. As I used to be a huge fan and evangelist, even gold-partner (I think I have answered over 5000 questions here over the years), SC abused me with my scriptcase .nl and .eu website and finally took off my gold-partner ship. I was not informed because the organization does not communicate with anybody. I stopped defending Scriptcase as I think that they had, have, and will have a significant quality issue. You all confirmed that in this thread.

I have a history of positive criticism, and it’s a fact that you catch more flies with honey than with vinegar. But that being said, I stopped defending Scriptcase. I find it amusing that we are angry with a member, and apparently accept the fact that SC is delivering buggy versions over and over again. Because nobody is really facing the company. I did, with the above result.

We all know that SC is not responsive, so where else to put your frustration?

Since the early days I tried to set up a community and a beta team to help SC improve the quality of their product. In those days (Carlos Lacerda and Marcia Auroro) I had close contacts. I was promissed a lot, and the current status after years is that nothing has changed.

I don’t want to repeat all that I wrote on this in the past. But looking at the pricing vs quality, the amount of ‘patience’ you must have when you encounter issues, the ‘hidden’ bugtracker (you never know if your issue is being picked up and when it is solved), I can continue for ages.

I think this should change. Perhaps shouting on the forum is not the way. But I’m curious about ideas how we can - together - help SC to get their quality on track.

It’s to late for my personal license, most of you know that I have a product of my own. But I still would like to see a better and more reliable Scriptcase.

[maxi]

Albert.

I appreciate your post.

A long history of enthusiasm and delusion behind it which I do perfectly understand and believe me … it is mutual.

I think it is the market that eventually decides if a product is successful or not.
I have no access to NetMake financial data nor I know who really owns Netmake to say if SC has been successful so far or not.

Certainly there are competitors but if we are all here discussing about SC it is because we have not yet found ( at least not me ) other convincing alternatives.

Personally I think SC supports have improved over the years but certainly there is still much room for improvement.

I dont think they don’t listen to customers.
They do ask you, for example, to rate the support answers and they strive to speak some understandable English. These are the support L1 people.

Developers are another story. I don’t even know how many they have and how they select and prioritize the bugs to be fixed. I don’t think they have many.

I am convinced that much of the frustration we all experience is due to two major factors:

1. Language barrier . Should I be able to speak portuguese I would pick up the phone and call them.
2. Lack of developers.

Anyway today I am happy because three thickets I have opened last week have been closed in less than a week.

[aducom]

Hi Maxi, you are an old user like me. You have a similar experience. The time they used Google Translate to translate the issues to Portuguese and back to English (causing answers that I could not relate to the question) is more-or-less behind us. That is an improvement for sure. But it hasn’t changed the company’s culture, prioritizing whistles and bells before the importance of bug fixing or - in this case - performing the necessary steps to solve this PHP thing. Especially when you’re short on resources. But my intention is not to drive people away from SC, but to help them get things on a standard we all can live with. It is great that they fixed a few bugs in a reasonable time, I have by far more examples of the opposite. But lets stay positive and hope that things have improved. That is in all our interest.

[jlocana]

Hello aducom. I am new in scriptcase and i saw your website. There is a way you to combine your phspeed with scriptcase.

Thanks

Jose

[aducom]

Not appropriate to answer that, but I’ve sent you a pm.