Skip navigation
Karen_Little
Karen_Little
Currently Being Moderated

Attribute validation error

Jun 11, 2012 2:47 AM

Hi - all of a sudden, successful code that I've been using daily, is throwing an error that reads:

 

Attribute validation error.

A duplicate attribute VALUE has been encountered. Attributes with the same name cannot be provided more than once.

 

 

Now then, I do not understand the above message at all.

 

In the first instance (on application 1), this is where the code stops:

 

30 : <cfif next IS 1> 

31 : <cfinclude template="admin/admin_tags/_getNames.cfm">

32 : </cfif>

33 :

 

In the second instance (application 2), this is where it stops:

 

 

The error occurred in E:/inetpub/wwwroot/littleviews/blogin.cfm: line 31

 

29 : 

30 : <cfif next IS 1> 

31 :  <cfinclude template = "_accessName.cfm">

32 : </cfif>

33 :

 

 

I'm also having trouble with <cfinclude. I tried "including" a different filename that resides in the same directory and CF tells me that it can't find the file.

 

As I use <cfinclude in a lot of places on other pages, I am NOT having a problem with it. But I'm am having a problem with the two applications above.

 

Karen

690 Views   7 Replies   Latest reply: Karen_Little, Jun 13, 2012 6:12 PM
 
Replies
  • Adam Cameron.
    Currently Being Moderated
    1. Adam Cameron.,
    Jun 11, 2012 2:54 AM   in reply to Karen_Little
    Report

    Possibly look ath the files being included, rather than the file doing the include.

     

    You could also run the code analyser over the whole dir: that'll turn up any compile errors like this in all files.

     

    --

    Adam

     
    |
    Mark as:
  • Karen_Little
    Currently Being Moderated
    2. Karen_Little,
    Jun 11, 2012 4:01 PM   in reply to Adam Cameron.
    Report

    Good advice, Adam. I checked my <cfinclude> line by line and did find a problem.

     

    At the moment, my problem is not resolved. I know a number of things that are NOT my problem at the moment (smile) and the only thing I can think of is that somehow I came to use a reserved word. So, now I'm changing the names of all my variables to see if that helps.

     

    I'm inching along with tests ending in <CFabort>

     

    At first, I thought that there was something about CF8 that made extracting information out of queries different, but if that was the case, my whole site would come down.

     

    Should I find that I did trigger a reserved word, I'll post it here.

     

    Karen

     
    |
    Mark as:
  • Karen_Little
    Currently Being Moderated
    3. Karen_Little,
    Jun 11, 2012 4:10 PM   in reply to Adam Cameron.
    Report

    Hummmmmm . . . now I'm thinking it has something to do with <cfqueryparam . . .

     

     

     

    
     
    |
    Mark as:
  • Karen_Little
    Currently Being Moderated
    4. Karen_Little,
    Jun 11, 2012 4:18 PM   in reply to Karen_Little
    Report

    o mah gawd in heven . . . between the time my code worked perfectly and when it stopped, I accidentally placed a <cfqueryparam in a <cfcookie tag.

     

    Thanks for pointing me in the right direction! My CF skills are rusty. I use them every 6 months or so and it shows.

     

    That said, session variables (the few I had) no longer work and I've had to replace them with cookie variables. Session variables would not carry over from page to page.

     
    |
    Mark as:
  • Adam Cameron.
    Currently Being Moderated
    5. Adam Cameron.,
    Jun 13, 2012 6:41 AM   in reply to Karen_Little
    Report

    I'm inching along with tests ending in <CFabort>

     

    You can avoid that sort of approach by using the Code Analyser or CFCOMPILE.  This sort of thing is a compile-time issue, so one doesn't need to run the code in context, simply see if the file compiles or not.  Both the C/A and CFCOMPILE will check all your code in one fell swoop.

     

    --

    Adam

     
    |
    Mark as:
  • Adam Cameron.
    Currently Being Moderated
    6. Adam Cameron.,
    Jun 13, 2012 6:42 AM   in reply to Karen_Little
    Report

    That said, session variables (the few I had) no longer work and I've had to replace them with cookie variables. Session variables would not carry over from page to page.

     

    I think you should pretty much try to fix whatever the issue is with sessions, rather than fall back to using cookies...

     

    --

    Adam

     
    |
    Mark as:
  • Karen_Little
    Currently Being Moderated
    7. Karen_Little,
    Jun 13, 2012 6:12 PM   in reply to Adam Cameron.
    Report

    I used to create dynamic websites for industry, but now I'm just maintaining a few personal and small client sites. In April, a spammer found a hole in my main site (mine along with hundreds of thousands of others), and left it's mark in my database. As I'm personally changing directions, I decided to shut down all my interactive areas, with just a few personal portals for myself. Should I get back into coding full time, I'll definitely look for those tools (she said sobbing, remembering Homesite). In the meantime, www.LetsKickScoot.com . . .

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points