CodeCharge Studio
search Register Login  

Visual PHP Web Development

Visually Create Internationalized Web Applications, Web Reports, Calendars, and more.
CodeCharge.com

YesSoftware Forums -> CodeCharge Studio -> General/Other

 codecharge problems- older vs newer versions

Print topic Send  topic

Author Message
rvp032582

Posts: 47
Posted: 02/08/2008, 12:43 PM

a former coworker had codecharge 2.1 on her comp, she built a site in it...i had to take over the project and build a calendar and i had codecharge 3.2....well it basically thru the whole site out of whack when i uploaded my new page/stuff to where i had to regenerate/debug and in some cases rebuild every single page of the site again. same thing happened recently once computer at work has codecharge 3.4 or 3.something...and my 3.something is different...so we kept getting weird errors and took a long time to fix and so on....

there is now codecharge 4.0 out...so now any clients that want new pages/new funtionality/new anything and whose sites were built with earlier versions of the software, it'll will take much longer to do b/c of the cryptic errors and zanyness codecharge spits out when the new files are uploaded etc (debugging).
it hasn't been too much of prob in the past b/c i had both codecharge 2.5 and 3.whatever on the old dead computer (i would use 2.5 when working on an older site). but i only have one version on this new comp, and i don't see a way to download previous versions of the software....so its a bit of a pickle....

i was working on a form earlier...i gave up and handcoded it , b/c i only had like an hour left to get it working and i had been using codecharge for nearly 2 hours to try to create it. ( i have a newer version of CC, the site it was for was built with an earlier version...) hand coding it took around 20 mins or less....
if i had the same version of CC the site was originally built it...it would've taken like 20 mins or as well.
but i don't....

basically sites built in the older version can get screwed up with new work is done to them in a new version and it's a hassle...that's pretty much it.

is there anytihng that can be downloaded or done about this? anyone else having similar probs?
View profile  Send private message
Vincent

Posts: 31
Posted: 02/08/2008, 2:14 PM

I will have to agree with you up to version 3.xx. I have been a CCS developer since version 1.0 and previously a codecharge user (basically since year 200). I agree and I always hated upgrading to a new version of CCS for the reason you've mentionned. I had at a time three different version of CCS on 3 different computers, a pain. So now, I don't know if this is going to be good news for you but I've been spending most of my day today converting my CCS 3.1 to 4.0 and miracle not 1 error message and I have web sites/projects in PHP, ASP and .NET. I cannot stop smiling :-) Furthermore, with version 4.0 you have a 3.xx version installed at the same time.

Vincent
View profile  Send private message
Vincent

Posts: 31
Posted: 02/08/2008, 2:15 PM

Well I meant year 2000 :-)
View profile  Send private message
DonB
Posted: 02/08/2008, 2:46 PM

You don't say what these problems are, but I wonder if there was
modification of the 'standard' code portions. My experience has been that
pages migrate to newer versions of CCS with virtually no pain. If the
standard (grayed out) blocks of code were edited, then there most certainly
will be issues with publishing under a newer CCS revision. Along about 2.1
or 2.3, some fairly significant changes to the page-encoding took place and
those involved significant conversion edits (although automated by CCS).

Within the 3.x range, I've found pages don't seem to have any conversion
edits done to them. But perhaps I've not utilized the bits that ARE
converted. Iknow that I've taken 3.2 pages and put them back into a 3.1
project and they still worked fine.

I don't want to say it sounds like you're doing something wrong, but it does
seem like you are having abnormal/excessive trouble upgrading. There's got
to be a deeper reason than just the version changing.

--
DonB

http://ccswiki.gotodon.net


"rvp032582" <rvp032582@forum.codecharge> wrote in message
news:247acbf025622d@news.codecharge.com...
>a former coworker had codecharge 2.1 on her comp, she built a site in
>it...i
> had to take over the project and build a calendar and i had codecharge
> 3.2....well it basically thru the whole site out of whack when i uploaded
> my new
> page/stuff to where i had to regenerate/debug and in some cases rebuild
> every
> single page of the site again. same thing happened recently once
> computer at
> work has codecharge 3.4 or 3.something...and my 3.something is
> different...so we
> kept getting weird errors and took a long time to fix and so on....
>
> there is now codecharge 4.0 out...so now any clients that want new
> pages/new
> funtionality/new anything and whose sites were built with earlier versions
> of
> the software, it'll will take much longer to do b/c of the cryptic errors
> and
> zanyness codecharge spits out when the new files are uploaded etc
> (debugging).
>
> it hasn't been too much of prob in the past b/c i had both codecharge 2.5
> and
> 3.whatever on the old dead computer (i would use 2.5 when working on an
> older
> site). but i only have one version on this new comp, and i don't see a
> way to
> download previous versions of the software....so its a bit of a pickle....
>
> i was working on a form earlier...i gave up and handcoded it , b/c i only
> had
> like an hour left to get it working and i had been using codecharge for
> nearly 2
> hours to try to create it. ( i have a newer version of CC, the site it
> was
> for was built with an earlier version...) hand coding it took around 20
> mins or
> less....
> if i had the same version of CC the site was originally built it...it
> would've
> taken like 20 mins or as well.
> but i don't....
>
> basically sites built in the older version can get screwed up with new
> work is
> done to them in a new version and it's a hassle...that's pretty much it.
>
> is there anytihng that can be downloaded or done about this? anyone else
> having similar probs?
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.yessoftware.com/
>

rvp032582

Posts: 47
Posted: 02/08/2008, 4:59 PM

thanks for the reply. a lot of the errors pertain to the classes.asp include file....they usually say something like a certain variable isn't defined...one such being CCSBR or CCSAMP (not 100% on that b/c i had to quickly undo what i did or go thru the 2000+ lines of code that CC generates in the classes file - hoping that deleting whatever line it says the error is on fixes the issue...before a clients notices it)
often times if i'm working on an earlier version CodeCharge site, where the client wants a new page or new functionality on a existing, i create the 2 admin _list and _maint pages. usally i'll get a "cannot be done with object is closed" type message with a 4digit line number in the classes file....not sure why it would do this...i'll start from scratch and recreate several times (the maint page)....eventually something works...and the problem goes away. i've only noticed this when i'm working on a site created in an earlier version of CC with a newer version of CC.
mainly its the classes file...i've noticed an FCKeditor will stop working if i upload and newer version classes file to and old version CC site...i have to spend time hunting down the lines the error calls too. basically newer versions of codecharge appear to code these pages different adding different variables/functions (which i dont know what their for...). so thats mainly the issue.

i like the new features newer versions of the software has. on paper CC is a really powerful tool, i'm just noticing a lot of problems/hassles when dealing with it sometimes....there's been quite a few nights working late on sometihng that i thought would've/should've taken a lot less time.....
it seems to generate a lot of code that while necessary to the CC generated site...it seems like way too much.

i'm not sure what vincent did to get no errors like that....and maybe i am doing something wrong...i'm not sure. while it would be great, unfortunately we don't have time to spend converting all our 200 sites to new versions of the software.....plus if clients noticed errors on their sites that could be bad.

it's a fast tool...just noticing problems with versions....i guess for now there's a real fix for it. has anyone seen probs with the classes.asp file imentioned in the 1st paragraph?
View profile  Send private message
cruisin

Posts: 31
Posted: 02/08/2008, 5:50 PM

I had a similar experience going from 2.3 -3.0 on certain pages. The quick work around I found was to save the page as a copy. Then copy the component from the copy back into the original, and delete the original component.

If you have any pages where you modified the source without using an event, this will also screw things up. I had a couple of those as well. You may have to compile them from scratch. If the page is just links, you can just copy and paste and it seems to recompile correctly as well.

View profile  Send private message
rvp032582

Posts: 47
Posted: 02/08/2008, 6:07 PM

oh ok. thanks i will try that next. it makes sense, i'll give it a try
View profile  Send private message
DonB
Posted: 02/08/2008, 7:50 PM

Those would be related to the new internationalization features I'm pretty
sure. It's possible that leapfrogging a version could be to blame, too.
Maybe the conversion doesn't do well if you don't hit the intermediate
revisions.

--
DonB



"rvp032582" <rvp032582@forum.codecharge> wrote in message
news:247acfb08e14f5@news.codecharge.com...
> thanks for the reply. a lot of the errors pertain to the classes.asp
> include
> file....they usually say something like a certain variable isn't
> defined...one
> such being CCSBR or CCSAMP (not 100% on that b/c i had to quickly undo
> what i
> did or go thru the 2000+ lines of code that CC generates in the classes
> file -
> hoping that deleting whatever line it says the error is on fixes the
> issue...before a clients notices it)
> often times if i'm working on an earlier version CodeCharge site, where
> the
> client wants a new page or new functionality on a existing, i create the 2
> admin
> _list and _maint pages. usally i'll get a "cannot be done with object is
> closed" type message with a 4digit line number in the classes file....not
> sure
> why it would do this...i'll start from scratch and recreate several times
> (the
> maint page)....eventually something works...and the problem goes away.
> i've
> only noticed this when i'm working on a site created in an earlier version
> of CC
> with a newer version of CC.
> mainly its the classes file...i've noticed an FCKeditor will stop working
> if i
> upload and newer version classes file to and old version CC site...i have
> to
> spend time hunting down the lines the error calls too. basically newer
> versions
> of codecharge appear to code these pages different adding different
> variables/functions (which i dont know what their for...). so thats
> mainly the
> issue.
>
> i like the new features newer versions of the software has. on paper CC
> is a
> really powerful tool, i'm just noticing a lot of problems/hassles when
> dealing
> with it sometimes....there's been quite a few nights working late on
> sometihng
> that i thought would've/should've taken a lot less time.....
> it seems to generate a lot of code that while necessary to the CC
> generated
> site...it seems like way too much.
>
> i'm not sure what vincent did to get no errors like that....and maybe i am
> doing something wrong...i'm not sure. while it would be great,
> unfortunately we
> don't have time to spend converting all our 200 sites to new versions of
> the
> software.....plus if clients noticed errors on their sites that could be
> bad.
>
>
> it's a fast tool...just noticing problems with versions....i guess for now
> there's a real fix for it. has anyone seen probs with the classes.asp
> file
> imentioned in the 1st paragraph?
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.yessoftware.com/
>

rvp032582

Posts: 47
Posted: 02/11/2008, 1:09 PM

a new page created in a newer version of CC yields:

Microsoft VBScript runtime error '800a01f4'

Variable is undefined: 'CCSUseAmps'

/admin/book_new.asp, line 385


i also deleted the line: "Response.ContentType = CCSContentType" on line 35

View profile  Send private message
rbaldwin

Posts: 172
Posted: 02/13/2008, 5:32 AM

i'm wondering if you are creating individual new pages or if you are

1. open project (entire project) in new version
2. press F9 to regenerate entire project
3. then make changes to existing pages or create new pages
4. upload entire project in new version.

for several years now i've been doing this with very few problems.
View profile  Send private message
rvp032582

Posts: 47
Posted: 02/13/2008, 6:56 AM

1. yes i have opened the entire project in the new version
2. no i haven't regenerated the entire project, b/c i assumed there'd be so many bugs/errors i'd spend hours going thru them

3 and 4 make sense. what i can possibly do is create either a subdomain or another directory and upload the new version of the CC generated site to that. unfortunately we can't risk our clients seeing errors or a down site etc. but yes i will try this too. thanks
View profile  Send private message
mljonzs

Posts: 124
Posted: 02/13/2008, 7:50 AM

We have a major application that was created in CodeCharge 2.3 and then was accidentally removed from CodeCharge (so I have to maintain it by hand now or recreate in CCS which I've not had time to do). I have had occasion where something new was needed that required a new web page. For these new pages and applications, I have created them in CodeCharge 3.xxx but they will not work if I try to put them into the same space as the old stuff - I see errors like ones you mentioned above and some of the base files like classes.asp and common.asp do not work if I publish CCS 3.xxx files in with the old. What I have successfully done for these is to put the new files into a different directory so they run with their newer files and the old CCS2.3 application runs with it's base files. This works well and allows me to add new things without breaking the older stuff....
_________________
What does not begin WITH God, will end in failure!
View profile  Send private message
rvp032582

Posts: 47
Posted: 02/13/2008, 12:49 PM

sounds like that's going to be the workaround for version control etc. kinda wished CC didn't code pages differently with each version like that. but it is what it is. thanks for the help, glad i'm not the only one frustrated out there
View profile  Send private message
Vincent

Posts: 31
Posted: 02/13/2008, 1:23 PM

Quote rvp032582:
a new page created in a newer version of CC yields:

Microsoft VBScript runtime error '800a01f4'

Variable is undefined: 'CCSUseAmps'

/admin/book_new.asp, line 385


i also deleted the line: "Response.ContentType = CCSContentType" on line 35


These errors are generated by the common file being originally created by a previous version of CCS. You are just missing new variables. This is probably due (as DonB has mentioned previously) to standard (grayed out) blocks of code that were edited which won't be modified by CCS while publishing to the server. One of my 3.1 project kept giving me errors (about CCSContentType, CCSUseAmps, etc...) I just had to update the code block "Initialize Common Variables" in my common file with one generated from a brand new CCS 4 project and it worked for me.

Check your common variables.

Vincent

Vincent
View profile  Send private message

Add new topic Subscribe to topic   


These are Community Forums for users to exchange information.
If you would like to obtain technical product help please visit http://support.yessoftware.com.

MS Access to Web

Convert MS Access to Web.
Join thousands of Web developers who build Web applications with minimal coding.

CodeCharge.com

Home   |    Search   |    Members   |    Register   |    Login


Powered by UltraApps Forum created with CodeCharge Studio
Copyright © 2003-2004 by UltraApps.com  and YesSoftware, Inc.