Not separately. I've only used a few cftextarea's which have the editor baked in. It'd probably be easier than trying to write the your own page builder. But your best bet is to try it out. See how well it fits in w/your app.
I guess what I would need would be a way to tell the code that here is the beginning of a heading tag word(or new list basically)
Yup. I suppose you could assume the 1st line is always a header, and every other line is a "detail" line. But like the previous method, it's only as solid as the data ;-)
There's one potential problem though. If the "detail" line doesn't have at least 1 "|", there'd be no way to distinguish it from the produce name headers
If every line has a hard carriage return at the end, that code won't work. The only way I can think of is to split the values on the carriage return, then check for a "|". If the line contains a "|" then it's NOT a header. Does that make sense?
Maybe it's lack of caffeine. But I've read the question twice and still don't understand what the data looks like. Could you give a sample of A) the values you're using (FORM.crossRefList, SESSION.crossRefList, productGroup) B) what the output SHOULD look like?
Because redirection occurs independent of the Yes/No values of that attribute
The AddToken attribute relates to client/session management. It has no affect on redirection. Only what's passed in the url. When addToken="yes", CF appends several client tokens (cfid, cftoken and possibly jsessionid) as URL parameters
It will help you solve your problem a LOT faster than us trying to explain how to use the various tools, so you can provide us with the debug info we need, ... one slow post at at time.
Please don't take this the wrong way. But if you're not familiar with db's, how to generate a table DLL or CF .. I think you need more assistance than we can provide. I'd suggest you should either ask to the person that gave you the code -OR- hire a CF person to fix it. Someone who knows the basics *and* has access to your code and db will be able to figure it out in no time.
No.. it's not fixed. You're misunderstanding what a cftry/cfcatch does. It only traps error messages. It does nothing to fix the problem. On your page, it will print out the SQL statement that failed.
ie <cfoutput>#cfcatch.sql#</cfoutput>
Post the result here. Then someone can help you figure out why the query isn't working.
No, any SQL has to be inside the <cfquery> </cfquery> tags.
Easiest thing to do is go back to your original code. Then add the <cftry> to very 1st line and add the cfcatch after the very last line of the page. It's not how you'd normally do it. But it's impossible to mess up :)
Nothing to do with your error, but the TRANSACTION is in the wrong place. In it's current spot, it doesn't do anything because there's only 1 statement in that cfquery. Transactions apply to multiple statements.
I'd bet dollars to donuts, whoever wrote that code meant to wrap it around both the UserDetails and UserContacts inserts..
Also, I was asking about what happens when you run the SQL directly in your db, *not* using cfquery. Using your IDE (Management Studio, etc..) you can easily view what tables and column exist.
The error message is pretty clear. The db can't find the object (ie Table) "Language". Run the query against directly against your db in MS SQL. Does it work?
Attribute validation error for CFMAIL.
The value of the FROM attribute is invalid. The length of the string, 0 character(s), must be greater than or equal to 1 character(s).
It's an error from cfmail. It's just saying the sender address cannot be empty. Where in your code are you using CFMAIL?
It'll work. But cfschedule takes some getting used to. I'd start out slow. Just create a small task that writes something to a log file first. Once you know it's working you can plug in your real page (after testing it separately of course).
Sounds like a good job for a scheduled task. Just create a cfm page that queries your db for the desired records. Then send a cfmail to each one. Once the page is set up, create a scheduled task using the CF Administrator, or cfschedule. Schedule the task to run your cfm script daily (or however frequently you need).
Well .. I don't mean literally by hand ;-) Just that you'd have 2 versions of the images: full sized and thumbnail. You'd still use the same CF code. But you'd only do it once and save them. It can be a batch script that cfloops through all of your images. Or code triggered when some event occurs, like an image is uploaded.
It's just too process intensive to run a resize every time somebody requests or refreshes the page.
CF9 has does have vfs. But image processing is time consuming. No avoiding it. It's usually better to just create thumbnails once and save them on disk. Resizing every time a user requests a page wastes a lot of resources.
I still want to know what they mean by "there should not be any conflicts" ;-) Conflict how? The answer will determine how to best approach it.
Providing a username and password in your cfquery tag will over-ride the default username and password for the datasource.
That is a good thought. Though truthfully I've always been hesitant to pass around the username/password at the query level. Any idea if makes a difference? Is storing the login at the dsn level any more or less secure than at the cfquery level?
Grab it from the #CFFILE# scope. After you do a CFFILE upload, that scope will contain all kinds of information about the uploaded file like: cffile.serverFile, cffile.serverFileExt, etc..
You mean store the file content in the db, not just the file path (ie "c:\path\myImage.gif")? While you can do it, it can drastically bloat your database. But if you really want to do it, here is an example. It's for Oracle but the overall process is the same for any db.
Just upload the file as usual ie using <cffile action="upload" ...>. But instead of storing the file path, you read the *contents* of the file into a variable. Then insert the variable's binary data into the database instead of the path. When you're done, you can delete the uploaded file.
Retrieving the file from the db is the same as any SELECT. Just retrieve the record, and use CFCONTENT, with the proper mime type to display it in the browser. If you need any help with that part, just let me know.
One thing to watch out for is your CF datasource settings. If you have files that bigger than 64K, CF will only return the 1st 64K bytes unless you enabled the "BLOB" setting in your datasource. http://awads.net/wp/2006/02/21/lobs-gotcha-in-coldfusion/
I just wanted to learn different ways on how do things so im not tied down to one way. Ill try what you have posted, but if sql injection is a major factor then ill just forget about it and use what i have.
That's always a good attitude to have. But with this one I'd say the lesson learned is "don't do it" ;-)
Every time I use dynamic sql - I end up regretting it. Though it's possible to make it safe from sql injection ... it takes a lot of work. Much more than with non-dynamic sql. Plus debugging syntax errors can give you a major migraine!
The problem is dynamic sql. Save yourself some headaches and don't use dynamic sql. It's never as easy as it looks ;-) Plus it's hard to debug and is a big sql injection risk if done wrong ...
But .. it doesn't look like you even need to return the query. You can just return the count. But dont' forget to VAR your cfquery's and use cfqueryparam
...
<cfset var qry = "">
<cfquery name="qry" ...>
SELECT count(status) AS Result
FROM table
WHERE status = <cfqueryparam value="#arguments.status#" cfsqltype="cf_sql_varchar">
</cfquery>
<cfreturn qry.Result>
...
I didnt know why it has 3 apostrophes
CF escapes single quotes to protect you from sql injection. The only way around it is to use PreserveSingleQuotes(). But then you're at risk for sql injection. Since you don't seem to need dynamic sql anyway, my advice is to avoid it altogether.
No. You shouldn't have # marks for the anchor "name" OR the closing </a> tag. That's what the validator is complaining about ;-)
I updated the code on my previous post. You need to get rid of all the empty anchors in the header (that only have an "id"). Then your code should look like this:
Header: <a href="#Z">Z</a>
The matching target in the content should be: <a name="Z" /> Zone Lighting
