search : legacy

select a category, or use search below
(searches all categories and all time range)

displaying top 100 results

Easily Moving from Legacy Code Hell to Modern CFML Heaven
Comment on Clean up your legacy code with Codechecker by Stewart
Comment on Clean up your legacy code with Codechecker by Kishore Balakrishnan
Clean up your legacy code with Codechecker
SOSensible

I am curious what we would rename it, Phoenix doesn’t seem to fit.

IMO, the whole defense of CF is dead is a dead discussion. When it comes up my response is standard. Legacy JS is dead, legacy Windows is Dead, legacy tech is dead. Have you used modern CFML?

Stephen Walker When are the articles from the legacy site going to be moved here?
2609610 CF-3822362 External U. Very much in favor of this. An update like this could revitalize the language while not sacrificing legacy work.
2613636 CF-3197321 External U. This bug prevents us from moving legacy code from Coldfusion 9
Anit Kumar Panda Stephen, can you share the links of article from the legacy site, you are referring to, for better clarity?
Comment on Clean up your legacy code with Codechecker by Charlie Arehart
2608408 CF-4100830 External U. This option works and is exactly what I needed. I agree this is not the correct way, but with the legacy application, it will allow me to upgrade and fix in a more efficient and timely manner.
2675973 CF-4010693 External U. We need better examples and references to things such as ways to convert legacy tag based code to cfscript based format
2610073 CF-3732993 External U. I definitely support this. It also gives a clean way to update some legacy code that may not have query parameters.
2610311 CF-3712010 External U. Adobe: Preserving legacy bugs because you've had to code around these bugs for so long that if we fixed the bugs we'd break your code.
2613522 CF-3298179 External U. Quietly failing on legacy apps in very unfortunate ways. User accounts saved on new CF10 box lose all permissions. I know how to fix, but this is problematic.
2613636 CF-3197321 External U. I am unable to create a DSN as required for legacy database reasons. This needs urgent fixing.
2608603 CF-4051460 Installation/Config : Installer ext-user Unable to install CF10 in mac 10.11 OS Problem: Unable to install CF10 in mac 10.11 OS Method: Result: Installation pop up displays "to install legacy Java SE 6 ". Expected: Installation should be done . Workaround: installs the legacy
AllenGP Identify Unlinked Pages – CF Builder We have a large number of legacy pages in our application’s code repository which are not linked to other pages. Is there a way in ColdFusion Builder to see which pages are not linked so they can be deleted? The post Identify Unlinked Pages – CF Builder
Comment on Clean up your legacy code with Codechecker by Charlie Arehart
Comment on Clean up your legacy code with Codechecker by murpg
2673312 CF-4127481 External U. Our legacy code base contains countless examples of this type of function. Imagine the dynamic output is a list of classes on an HTML element. Without the space between class names css and js references no longer work. It would be impossible for us to refactor our
2608442 CF-4093045 External U. Thanks for the update. I my opinion changing it later would mean even a higher risk, since at that point there would be even more legacy code to change. Do you have any idea how much later, later is?
2610566 CF-3695877 External U. We have been bitten by this more than once. On one server it got to > 70gb before we discovered it, and on another we forgot to turn that setting off when we went to production on a legacy server without a lot of disk space and didn't remember until it had filled
2612744 CF-3434473 External U. OK, what I think is clear here though is that whilst there might be an ER in here somewhere, the current implementation is not desirable? David, to be completely honest with you "but as a faster way to mitigate blocks of in legacy code" should not be the grounds
David Byers Fighting Stagnation: Learning how to grow your skills in a stagnant development environment Maintaining a legacy application can be a challenge, especially when the team is reluctant to try new techniques. Increment new methodologies gradually so as not to scare off developers stuck
2608368 CF-4110354 Language Luis Majano CFM templates do not parse == and/or != operators Problem Description: CFM templates do not parse == and/or != operators. This works on Lucee. Steps to Reproduce: {code:java} ` {code} Actual Result: Expected Result: Any Workarounds: Changing to legacy
requires the legacy Java SE 6 runtime which is unavailable for this version OS X. Note : It is also observed in CFB 3.0 . Expected: Workaround: ----------------------------- Additional Watson Details ----------------------------- Watson Bug ID: 4030251 External Customer Info: External Company
. This would allow for the community to move away from legacy code that should not be used anymore, and although very idealistic, if everyone did it, Adobe could start cleaning up the language of code that should be moved away from.
are affected and IE9 is the corporate browser. Due to legacy code, we are not using J2EE sessions on these servers. We are continuing to research, but any insight would be helpful.
2609837 CF-3759846 External U. Working on a legacy application that uses ODBC to Visual FoxPro. This is a requirement at this point and time. This is a fresh CF 11 install and getting the error stating the ODBC list is unavailable in the registry. This is happening with a downloaded installer
0.101213 (13-Dec-2010)), but the legacy support for flash requires a fixed pixel value. Steps to Reproduce: Use cfchart and attempt to use a percentage value. Actual Result: An error indicating the need to use a numeric value. Expected Result: percentage based layout to support responsive
2673429 CF-4126560 Legacy Area Travis Walters Code Analyzer Migration Tool Update 2 In the ColdFusion Administrator, I have not much experience using the "Code Analyzer" tool that has been there in previous releases and I have a few questions that might lead to some enhancements: Is there anyway
2597677 CF-3042987 Legacy Area : CF Anywhere Federica Lotti Bug 85405:if I make a cfdirectory type = "list", if the folder there are files that contain the word "report" (lowercase) that is read and printed by CF as "MyCompany QuarterlyReport" Problem: if I make a cfdirectory type = "list
2682485 CFB-4052048 Installer : Standalone Installation CFBuilder3.0 do not get launched in Mac 10.11 after installation Problem: Unable to launch CFB3.0 in Mac 10.11 after installation Method: Result: “CFBuilder” cannot be opened . This application requires the legacy Java SE 6 runtime which
2016 Update 3 REGARDLESS of encoding type: form fields disappear from form.fieldnames Adding this.serverSideFormValidation="false" to the application.cfc DOES prevent the behavior, but some legacy parts of our application still rely on that validation.
themselves really don't do much to help my argument. Microsoft does do an excellent job with the way they present their examples, so tab-based wouldn't be a bad approach. Regardless, the docs also need better examples and a good description of how to transition legacy tag-based code to script
2613603 CF-3207170 External U. I will not be able to provide the source code where this is occurring. Even if we could it would be a bit difficult as we see this occur where there are a large number of files involved through several cfc function calls. One example is our legacy in-house built
effect. From my point of view that runs very fast. If you want to change that to gain an performance boost, you propably have to completely shut the inpection of the settings on every request down. I doubt that this is possible without breaking a lot of legacy applications. Just one example: People
2602148 CF-3037176 External U. With every new release, Adobe adds more and more built-in functions that break lots of legacy code. Please remove this name conflict check because most method calls are made against an object (CFC) and are already disambiguated. The very fact that a simple
critical move. This would provide the following benefits:1. Legacy technology would not need to exist within the product2. Users could replace specific legacy plugins with their own versions . cfreport, for example, is so old and outdated it is not relevent to modern BI. If a user could replace
must when working with legacy databases, as it stands now if a legacy database has no ID then ColdFusion ORM can't work.I think you guys need to look at GORM here, because there are certain things that should be just given. For more information also see ticket #74806 where this was supposed to have
of CF 2018 and what the future brings. Why does almost every CIO think that ColdFusion is dead? So often it happens that I come across a CIO that thinks CF is dead or dying in a legacy land. One of the reasons why is […] The post Adobe ColdFusion Vision for the Next 10 Years, with Rakshith Naresh
ColdFusion Webinars 2020 ColdFusion for the Next Decade — All about the Buzzworthy ColdFusion 2020 (Webinar by Adobe) Adobe ColdFusion Developer Week 2020. ColdFusion Webinars 2019 Continuous Security for your CFML code with Fixinator Webinar with Pete Freitag Clean up your legacy code […] The post
.1.4 (Build 0001) Tomcat Version 9.0.10.0 Any help would be appreciated as we are evaluating CF 2018 to use with a legacy application that requires a single ODBC data source to run successfully. This is a show stopper unfortunately.
.cfc, but it breaks legacy applications which runs on old system.
to an escaped sequence in DateTimeFormat, characters in the sequence are omitted, or the function parses mask-characters Steps to Reproduce: Actual Result: 2016.02.02 AD 'P' 16:41:21 EST Expected Result: 2016.02.02 AD at 16:41:21 EST Any Workarounds: not really... the legacy date/time functions don
2608883 CF-3971110 CFForm Justin Treher Stop cfform server side validation when not using cfform/cfinput. Problem Description: Legacy issue with server side form validation still happening with form fields named in such a way that will trigger validation. This typically catches people
2608888 CF-3970987 CFForm Justin Treher Stop cfform server side validation when not using cfform/cfinput. Duplicate ID: CF-3971110 Problem Description: Legacy issue with server side form validation still happening with form fields named in such a way that will trigger validation. This typically
touched for years. Steps to Reproduce: Install the CF10 Update 15 on a CF10 enterprise environment on a per instace basis Actual Result: The server updates page broke and started showing errors. One of our legacy queries started returning commas instead of empty strings. Expected Result: No errors Any
, 4); Actual Result: Corrupt speadsheet file, containing multiple duplicate mergeCell tags in the underlying OOXML. Expected Result: Valid spreadsheet file. Any Workarounds: Selecting the legacy XLS format, or avoiding the specific (but fairly common) conditions described above, or postprocessing
2598136 CF-3041700 Legacy Area : Usability Monte chan Bug 83426:When there is only one data point to plot in Scatter, cfchart ignores the specified scaleMin value and always uses zero Problem: When there is only one data point to plot in Scatter, cfchart ignores the specified scaleMin value
2598414 CF-3041360 Legacy Area : Eclipse Wizards Steven Erat Bug 82729:(Watson Migration Closure)Please provide ColdFusion Extensions for Eclipse for Flash Builder 4 and ColdFusion 9 support Problem: Please provide ColdFusion Extensions for Eclipse for Flash Builder 4 and ColdFusion 9 support
2600024 CF-3039471 Legacy Area : CF Anywhere Brian Carr Bug 79140:(Watson Migration Closure)I realize that this may sound a little "out there", but I think would be extremely beneficial Problem: I realize that this may sound a little "out there", but I think would be extremely beneficial
2600118 CF-3039370 Documentation : Examples Adam Cameron Bug 78937:Spreadsheet function documentation is still excel-centric in places Problem: Spreadsheet function documentation is still excel-centric in places . I imagine this is a legacy of the functionality suite originally being based
2600454 CF-3039009 Legacy Area : CF Anywhere Paul Kukiel Bug 78160: within a method now created a attribute itn e variables scope instead of being ignored Problem: within a method now created a attribute itn e variables scope instead of being ignored. If a variable exisitns int e variables scope
2602201 CF-3037120 Legacy Area : Usability todd sharp Bug 74681:When trying to rename a file with cffile, if the source and destination are the same file name CF will throw an exception such as: Problem: When trying to rename a file with cffile, if the source and destination are the same file name
2682272 CFB-4130095 Installer : Standalone Installation Steve Walker Cannot run on OS X El Capitan Cannot run on El Capitan due to reliance on outdated Java version. "This application requires the legacy Java SE 6 runtime which is unavailable for this version OS X
this with a couple of legacy web sites. Update 6 and before had no issue with it. Actual Result: 400.0 IIS Error Expected Result: Web page is displayed Any Workarounds: DNS edits
For* functions, but as a faster way to mitigate blocks of in legacy code.
Yang External Customer Email: External Test Config: My Hardware and Environment details: Working Config: -- Win 2003 Server Enterprise SP1 -- ColdFusion 9,0,1,274733 -- Oracle 10.2 (legacy) and Oracle 11.2 (production) Non-working Config: -- Win 2008 Server R2 -- ColdFusion 10
.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:101) at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:154) at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:42) Caused by: java.lang.ClassNotFoundException: javax.jms.InvalidSelectorException at java.net.URLClassLoader.findClass(Unknown Source
daniel fredericks I have seen more and more people talking about getting a good Developer and training them...I think the issue might be a lot of CFML work is legacy/maintenance so it is tag based...if more of that works could be converted to or done in cfscript, a mid level JS developer could come
legacy project an Excel guy or whatever ran on a "server" under his desk, until the enterprise ended balkanization and now they want to migrate it to a server platform for which they have experienced developers - and nobody wants that platform to be CF because, well, for the very few people who do have
2608179 CF-4170204 CFForm : HTML Gary Stanton 'serverSideFormValidation = false' stops validation errors, but does not stop omission of fieldnames Problem Description: In CF9, a flag was added to disable the legacy 'hidden fields form validation' that occurrs on form fields in the format: xxx
2673428 CF-4126561 Legacy Area Travis Walters Code Analyzer Migration Tool Update In the ColdFusion Administrator, I have not much experience using the "Code Analyzer" tool that has been there in previous releases and I have a few questions that might lead to some enhancements: It appears
this and it will run ok. Actual Result: Now use the Code Analyzer in Adobe ColdFusion 11 Administrator to analyze this file and it would report an error stating that the getmetadata function is new in ColdFuion10 and the UDF name must be changed to avoid conflict in our legacy code. Expected Result: No error must
an easy way to protect against XSS, especially in legacy code bases. ----------------------------- Additional Watson Details ----------------------------- Watson Bug ID: 3434473 External Customer Info: External Company: External Customer Name: David Epler External Customer Email:
2597108 CF-3114283 Legacy Area : CF Anywhere Travis Walters Bug 87281:-(Watson Migration Closure)CODE A: SELECT INSTITUTION_ID, INSTITUTION_NAME, INSTITUTION_CITY, COUNTRY_ID, INSTITUTION_DEGREES, INSTITUTION_START_DATE, INSTITUTION_END_DA Problem: CODE A: SELECT INSTITUTION_ID, INSTITUTION
2597294 CF-3044017 Legacy Area : Usability Michael Zock Bug 87092:CF's parseDateTime does not understand float values generated by interaction with timespans (e Problem: CF's parseDateTime does not understand float values generated by interaction with timespans (e.g. #parse
notice that if I have declared a cfargument in my method, the AS object is passed as if it were a struct being passed in positionally which is breaking my legacy code. Should this be considered a bug, or was I simply being dependent on an unintended feature in CF 8? Method: Result
if created in the hbm.xml files (Although direct support in CFC entities would be even better!) Property grouping is a way to achieve some exotic joins that, although uncommon, could potentially be needed from time to time, especially in cases that you’re dealing with legacy databases in with strange
2601994 CF-3037353 Legacy Area : Usability Patrick Heppler Bug 75158:(Watson Migration Closure)When using ColdFusions built-in AJAX features, you're unable to validate your site as XHTML Strict!!! It would be nice, if the ColdFusion generated JavaScript would be either placed in a separate file
5116440 CF-4203531 Database CF 2016 - Query Caching Issue - cfstoredprocprocedure Problem Description: We’ve encountered query caching issues in our recently migrated CF 2016 environment. Our legacy system is CF 10, where the same caching procedure is working perfectly fine. See below for more
this was an issue in the esapi jar and is fixed in the most recent version esapi-2.2.0.0.jar I was working with legacy code and replaced all occurrences of HTMLEditFormat with EncodeForHTML and JSStringFormat with EncodeForJavaScript. This led to double encodings which I wanted to correct by setting the second
regardless of why or how it's being created. (If it's being populated with persisted entity data is irrelevant) The shoddy legacy behavior of not having a proper constructor is an unfortunate embarrassment in the history of CFML that I've been happy to see made right in newer functionality. Calling a
2613071 CF-3347145 External U. I am adding a vote because I have an 8 year old legacy application that stores its date/time values as their UTC equivalents -- in SQL Server 2005 which has no concept of timezone, no less; the fact that the values are UTC rather than local New Zealand Time (UTC+12
.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:884)at flex.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:121)at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:158)at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:44)at flex
another site that still uses global settings in the CF administrator. That site, "Acelink", also uses Application.cfm since it was built many moons ago. It still runs on pre-CF8 legacy code. In the CF Admin, I have a custom tag path that points to the root of the acelink web site directory. Again
.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:101) at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:154) at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:42) at flex.messaging.endpoints.amf.BatchProcessFilter.invoke(BatchProcessFilter.java:63) at flex
.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1400) at flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:1005) at flex.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:103) at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:158) at flex
by providing two more granular forms of defaults for datasourcing before 9 launches and legacy Luddites can argue backwards compatibility issues. to override the application default on a per-request basis and ( and similarly attributes.datasource where appropriate ( cfthread, etc. ) ) to override both
2601892 CF-3037463 Legacy Area : Usability Brian Meloche Bug 75361:(Watson Migration Closure)CFTABLE and CFCOL have been around for a very long time, but their usefulness has been limited due their lack of CSS support Problem: CFTABLE and CFCOL have been around for a very long time
.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:117) at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:158) at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:48) at flex.messaging.endpoints.amf.BatchProcessFilter.invoke(BatchProcessFilter.java:67) at flex
.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:757), flex.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:117), flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:158), flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:48), flex
.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBroker Filter.java:121) at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:15 8) at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java: 44) at flex.messaging.endpoints.amf.BatchProcessFilter.invoke(BatchProcessFi lter.java:67) at flex