tmgkatrina
Posts: 2
|
| Posted: 11/09/2009, 7:27 AM |
|
We have an app that works perfect under IE but the same pages in FireFox have issues with Text Fields.
In FireFox the user cannot enter any spaces or special charactors (for example in an address field). No error is generated - the keyboard input for the space and/or special charactor is just ignored.
Code is PHP on MySQL. Has been upgraded to CodeCharge 4.3 and regenerated (no difference).
If I create a brand new page (not connected to a DB - just a form with a text field) then there is no problem.
If I add a new text field to the existing form but don't connect the field to a DB field - still has a problem.
This website has multiple code charge apps in various places. The other apps work fine.
Field datatypes in question are both Text and Memo. Doesn't matter if required or not. No validation being done. No JavaScript being used. Database field is Varchar(65) Not Null.
Any ideas?
- Katrina
|
 |
 |
datadoit
|
| Posted: 11/09/2009, 1:27 PM |
|
Take a peek into the stylesheets to make certain nothing's going on there.
|
|
|
|
tmgkatrina
Posts: 2
|
| Posted: 11/09/2009, 1:41 PM |
|
Thanks for the reply.
In trying to research it I did the following;
1. Added a new 2nd record below the record in question.
2. The 2nd record had the same problem.
3. Deleted the 1st record and Voila - the 2nd record worked fine.
They were both using the same css.
I went back and looked and removed my AfterInsert code. Issue still there. The main code had been modified only in the Operation() method. I doubt that was it because the issue occured prior to any of that code being triggered.
Stumped me for sure. I ended up recreating the page - direct copying my custom code and now everything works fine.
Odd - would really like to know what caused it. I wonder if it were something as simple as a missing html tag?
- Katrina
|
|
|
|
datadoit
|
| Posted: 11/09/2009, 5:50 PM |
|
Seen oddities like this also. Have learned to make backups of files
before altering (CVS), and set an internal time threshold for trying to
fix problems before reverting.
|
|
|
|
damian
Posts: 838
|
| Posted: 11/09/2009, 7:44 PM |
|
if you have checked your code and it really is dolng something strange - create the page again - the speed at which you can do this in ccs makes it a viable solution - unfortunately it is also the complexity of the generated code that makes troubleshooting the real cause painful...
_________________
if you found this post useful take the time to help someone else.... :)
|
|
|
|
whiterabbitwond
Posts: 28
|
| Posted: 11/11/2009, 11:49 AM |
|
Gentlemen, I could not agree more on both these points below. Which is why I both love and loath CCS (depending on the day).
Graduating through the school of hard knocks, my system looks like this, and I haven't been burned since I started doing this. (burned = losing days of code because of ccs corruption).
When coding / testing something new, I quick publish to server often until i get it fairly stable. then save. after every save, i then right click the project folder in windows explorer and zip a copy (with winrar) which auto added a time stamp to the filename. Then repeat that process everytime I finish a change i'm happy with. The time it takes to do this is about 10 sec. I find this faster than cvs or svn when it is just me coding on my own. I repeat this every 5-60 min.
Then every day my backups are backed up offsite with jungledisk.
On heavy coding weeks, i have to revert to a previous zipped version at least once when ccs has borked my code. Those little 10sec backups have saved me hours of lost work.
This is especially relevant when working with complex pages. For simple pages, I agree with Damian below. But for complex, that is not an option.
Cheers, david
Quote :
Seen oddities like this also. Have learned to make backups of files
before altering (CVS), and set an internal time threshold for trying to
fix problems before reverting.
datadoit
if you have checked your code and it really is dolng something strange - create the page again - the speed at which you can do this in ccs makes it a viable solution - unfortunately it is also the complexity of the generated code that makes troubleshooting the real cause painful...
damian
|
|
|
|
damian
Posts: 838
|
| Posted: 11/11/2009, 6:05 PM |
|
i usually only work in ccs for a few hours a nighht a few days a week so i dont go to quite the lengths that david goes to but i do something similar.
i do lots of quick publishing and save once its right.
if it messes up then i close the page without saving and re-open to continue
i zip up the project at the end of each day
i dont usually do too much complex stuff (well its complex for me but not for most of you real programmers)
_________________
if you found this post useful take the time to help someone else.... :)
|
|
|
|
