Download Scriptcase Full Version

[Beronike Watkin]

Youmean in production?? Go to your (assuming you use windows) Program Files/NetMake/v7/components/php dir (Or Program Files (x86)/NetMake/v7/components/php and check the php.exe version via right mouse, properties, details.

Here is a fragment of the post from [SIZE=20px]MAY/2015[/SIZE]. Backup/Restore has not been fixed until now. This is one of the reasons I would not recommend SCRIPTCASE to other developers until the NetMake paradigm changes. Bugs remain unfixed for months (if not years).[/B]

-8/bugs-aa/9093-can-t-restore-project

Furthermore, as Giu mentioned to you in the previous topic, the one you quoted me, its been a while since we had any problems with backup / restore functionality.

The last one was back in early SEPTEMBER, and it was fixed in the other week. Backup / Restore is truly stable right now.

The Import issue was reported 2 years ago or so. My license issue came up in December/2016 when I had to renew it. I offered download link to NM but they said they will not going to use it. Email would not work - files are to big. I will think about dropbox to see if I can use it. The tips about the installation might be helpful for some but I have already managed my installation issues and seems the SC works fine, although I still cannot RESTORE older projects (made with SC8). This problem always happens to me when I need to upgrade, reinstall etc. Otherwise it works fine, so there is something that is happening during Installation or Upgrade that makes those files incompatible. I undesrtand your security concerns but handing all users backups while only single user can have numerous files in sizes of 30-100Mb sounds rather insane. I hope you are right about the fact that only older projects have the issues. I was able restore project from November/2016 without issues but the ones from Spring/2016 will not work. I will try to put my backup files on my FTP sever and PM you with the credentials so you can download it and fix it.

Backup and Restore had serious issues some time ago, and has I told you the routine was remade and is stable now.

Thank you for understanding Arthur, please PM @John_L_Santos with the credentials. He will assign someone from test team to handle it for you.

Well, the question is, in which version did you make your backup? There are several ways to export or create a backup, you need to be sure that you use the correct restore. If you have made a backup in an older version, you must reinstall this one and start from there.

the diagnosis menu is only accessible on my development environment, but not in the deployed apps on the production server. I want to check what version of scriptcase is deployed on the production server

When you deploy, then there are no dependencies on SC anymore. But I can imagine that you want to keep track of when to deploy the runtime, as deploying new versions of your application is way faster if you only deploy changed files. But I still recommend uploading the full story every time. However, if you require the information, consider storing a text file with this information, that you can retrieve an display.

this is inaccurate. When I deploy applications they still depend on the deployed scriptcase core, for example the SC core file _lib/prod/lib/php/nm_ini_perfil.php is not modified when I deploy apps and also the deployed version number appears to be in _lib/prod/lib/php/ver.dat

I wanted the version of the SC engine that runs and displays the deployed applications in the production environment, not the engine that produced the applications in the development environment. You found the correct solution %Your app url%/_lib/diagnosis.php which shows the version of the deployed SC engine

i have an old application lets name it officemanager made with scriptcase 9 that is working on a host server with php 7.3 but now i upgraded my hosting php to 8,1and that application (officemanager) that was builded with SC( 7.3 dont work anymore

thank you for the answer, but i dont have the code anymore. after i deployed the application back in 2019 i deleted my code project. and now i have only the application who worked very fine untill i made an php upgrade to 8.1. so i will downgrade the php to have it worked back. anyway thank you for the fast answer.

Hi. I would like to access the actual SC project name and the version number (like 1.1.0) that come form the project settings. I would like to access them as some sort of global variables, for use in my code as well as titles in apps, etc.

Thanks - I will add this to the feature suggestion. It would be useful to know what version of the SC and what version of your project created a particular deployed installation. If I create my own session variables it is just one more thing I will probably forget to update

Thanks for your input - Peace,

Jamie

There are also some vriables which are used throughout SC but are not explained anywhere

For example I have found several places showing some vars like: .$app

those show up in the security generated module but I was not able to find any help or description on what it is and how to use it ?

ok, here it gets a bit complicated. I would like to place a version number on the main menu (which is TreeMenu in my case), but before the user gets to it there is a Login App first to grant an access. Would I use the code in a Menu or in a Login App ?

The best scenario for me would be to store the version umber in global Var, so then I can use it anywhere, anytime

Yes , i want to use Bootbox ( ) which requires Jquery 1.9.1 as it uses Bootstrap 3 Javascript. This is on a control application , if I add the references to the application for the versions of Jquery and Bootstrap that Bootbox requires , some of the fields stop working (datepicker timepicker) , and the select fields loose their formatting obviously they require 1.8.2.

Beside the version control within the scriptcase, is there a way to store the scriptcase code in a code repository like github so that we can perform a kind of version control? and perform code sync automatically?

Hi,

the problem is not when it comes out BUT what can we expect, how many new bugs? and when will they make versions that solve problems and do not introduce others? better in version 9.6 in addition to solving at least the most annoying bugs.

obviously is only my opinion.

Scriptcase uses many old versions which might be the reason why it works, and perhaps you are not using things that are requiring higher versions of PHP. But if I understand it right, the next version of Scriptcase has upgraded versions of the embedded modules, and if that is the case, it will most certainly break running under php Hello Paul, thanks for your answer, it works only in the menu, I was looking for a command that would work even in the form, to display the form on the Mobile as the Desktop version.

Unfortunately Script Case 8 has many limitations in the mobile version.

I agreed with your statement about how unfortunate it is that SC8 has too many limitations in the mobile implementation. Until it is improved in future upgrade, we can not really use the mobile version to properly display grid/form on mobile devices. Mobile menu is not that great either but at least it is acceptable.

I ended up falling down this rabbit hole due to a need to control the version presented to the user due to a bug with uploading and downloading files with paths that include variables in the mobile version. (e.g. /file/[user_id]/)

$_SESSION['scriptcase']['display_mobile']

determines whether the version of the page displayed is the web version or the mobile version - something most obviously seen in the toolbar version shown. (but see below!)

I have a project ready to deploy in my test linux server. Apart from installing Apache PHP on the linux server do I need to install scriptcase too? And in what folder on the server do I deploy the project.

My plan is to install scriptcase on the Linux server that way I can get the correct version of Apache and PHP installed that is used by scriptcase. Is that a good route or should I install Apache and PHP manually?

*** if you are not in a debian derivative the folder could change, in that case search in google where in your linux distribution does the web apps has to be installed (this is a easy find, since it is a recurrent cuestion)

After updating my MAC to Sonoma 14.2.1 my scriptcase standard installation 9.10.001(2) stops working too.

I have a second apache and php8.1 installed from homebrew for my mariadb installation listening at port 80.

After modifying my homebrew apache and homebrew php8.1 according to the available scriptcase manual installation instructions and granting write access to the wwwroot and underlaying directories my scriptcase is back running and compiling without problems with the homebrew apache server.

what you do when upgrading project version that is already in production?

assuming many new applications were added to project in development

now we have 2 database, one in development and one in production which is already having logs and users and transaction data

is it practical to add many applications to development and also add the required new users groups and give all necessary permissions all in development, then just replace the table of mysql with the production version database?

basically for discussion to what you guys are doing when having production version running and meanwhile you have a new version in your development that you want to publish, that involves many new applications, users groups and permissions for each application

@MikeDE - I understand your point about adding new applications. Often that requires (in my case) changing a common menu application, adding new applications to the security tables, which creates more deployment risk and the need perhaps to test more before releasing. That said, I find that when I deploy even a single application, with no library updates, SC creates new files in _lib. I am not sure why. It also creates a new index.php in the project root. So, there are mysteries (at least to me) about why all this unexpected stuff happens, which leads me to be more conservative about development system updates and _lib updates.

3a8082e126