• Archived  

By snow2cold - March 21, 2007

We are starting with a new install of Article Manager 2.

I'm getting this error whenever I try to add a new category.

Error: DBD::mysql::st execute failed: Out of range value adjusted for column 'depth' at row 1 at (eval 105) line 18, <DATA> line 586.

I can edit & add articles & edit categories.

Re: [snow2cold] Out of range error when adding a new category

  • Archived  

By deniseb - March 21, 2007

Hi snow2cold,

Thanks for the post!

I'm not actually sure what may be happening here, what you may want to do is fill out a support request with your ftp details. This way we'll be able to connect with your server and take a closer look at what's happening here. :)

You can fill out a support request here:

https://www.interactivetools.com/support/email_support.cgi

Does this help? I look forward to hearing back from you soon!

Re: [snow2cold] Out of range error when adding a new category

  • Archived  

By deniseb - March 23, 2007

Hi snow2cold,

Thanks for the follow-up!

I'm actually not sure what may be happening here, however we are going to see if what we can come up with based on the info you have provided. Once we've taken a closer look at this we'll post an updated message for you. :)

In the menatime if you have any other question please feel free to ask.

Re: [snow2cold] Out of range error when adding a new category

  • Archived  

By Donna - March 23, 2007

Hi there!

Even if you're not able to give us FTP access, would you be able to fill out the support request form? You can fill this in here:

https://www.interactivetools.com/support/email_support.cgi

Since this is a rather odd situation, I think it'll be a little easier to take it up via email. :)

Details about where your software is installed and a username & password to access the admin section would be helpful as well.

Thanks! I look forward to helping you. :)
Donna

--
support@interactivetools.com

Re: [Donna] Out of range error when adding a new category

  • Archived  

By snow2cold - March 28, 2007

The problem is now resolved - we tried a newer version of Article Manager (2.12) and an older version of MySQL (4.1.13) and were able to make things work.

Thank you.