Copying an application into another project always results in run-time error

Scriptcase 7 Bugs
#1

I tried to copy an application of one project into another project in the IDE. Just check the selectbox and then use copy in the footer. If you then go to the new project, compile and run you get an error like this:

Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in C:\Program Files (x86)\NetMake\v7\wwwroot\scriptcase\app\DOHMWeb\bhr_dohmaccess\bhr_dohmaccess_apl.php on line 1026

I checked all settings in both projects, but they are the same so I don’t know how to solve it. I have posted this question to SC support but they are still struggling to get the problem reproduced. But for me it’s a consistent error, I tried from other projects too with the same result.

Now the problem is in the logging. The original application has a logging option, the new project has not. So while copying the logging stuff persists even if the main project has no logging.

#2

[QUOTE=aducom;24089]I tried to copy an application of one project into another project in the IDE. Just check the selectbox and then use copy in the footer. If you then go to the new project, compile and run you get an error like this:

Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in C:\Program Files (x86)\NetMake\v7\wwwroot\scriptcase\app\DOHMWeb\bhr_dohmaccess\bhr_dohmaccess_apl.php on line 1026

I checked all settings in both projects, but they are the same so I don’t know how to solve it. I have posted this question to SC support but they are still struggling to get the problem reproduced. But for me it’s a consistent error, I tried from other projects too with the same result.

Now the problem is in the logging. The original application has a logging option, the new project has not. So while copying the logging stuff persists even if the main project has no logging.[/QUOTE]

I tried and works ok. I suppose you tried to copy more than one time, true?

Don’t understand your last sentence. If original app has logging, normal behaviour is to copy with this configuration to new application.

#3

[QUOTE=Giu;24090]I tried and works ok. I suppose you tried to copy more than one time, true?

Don’t understand your last sentence. If original app has logging, normal behaviour is to copy with this configuration to new application.[/QUOTE]

If you have an application with active logging and you copy it then all is in the new project. But it simply generates an error at runtime. And all connection settings etc. are the same. I tried it too on a small app which gave the same result. I could track the error on the spot where it actually it trying to put things into the log table, so I guess something is wrong there. Other problem which occurs is that from the menu I get a very tiny IFrame where the application is run at, I’ve seen that before.

I managed in a small application to create the logfile and then copied the application into this project which looks ok. So I guess that if you create a new application, setup the logfile, then import it should work, but I don’t get the nail behind it.

#4

Ok, I found it. It’s a work-around, but as long as it works:… if you have created the new project and imported the application to be copied containing logs you need to go to tools -> log and the edit. Check the ‘delete if excists’ checkbox, then continue. If you do not do this you will not be able to run your application due to obscure errormessages.

#5

Thanks for share Albert.

#6

Hello,

Issue reported to our bugs team.

regards,
Bernhard Bernsmann

#7

are you referring to the tools menu? O don’t have a “logs” item in that menu where is it?

#8

I found it! It is in the Modules Menu in Scriptcase 7.1. This solved my problem. Thanks for your wisdom, OH Great One!

Regards,
Peter Schwitz