"An error has occurred adding the content type source"

Can you, please, post specs of the server you are installing it to?

Did you install from tar.gz or zip?

Thank you

Some specs that could help:

PHP version and php modules enabled.
Values of the: max_execution_time and memory_limit php.ini variables
RAM and CPU of the server.
MySQL version

Also, if you can wipe-out the broken installation and (in case you hit the same error) - post the screenshot, that would be great.

thanks

Hi,

I have the same error. Please see the attached screenshot of the last installation screen.

Did I have to supply all API-Keys for a sucessful installation? Maybe this is the error, because I only provided a key for open calais.

best regards, Tom

Thank you for the info. very helpful. We will look into this and get back to you soon.

Can you, please, also look in Apache error logs - see if there's any more specific error message there?

Thanks

I get the same error. There are not errors in my apache logs. I did a clean reinstall and hit the same error.

php memory 192M
php execution time 1000

php-5.2.10-1.el5.remi
mysql-server-5.1.39-1.el5.remi

I made a complete reinstall and there are no errors in apache logs. I also set up an extra logfile for php-errors there are also no errors found. Only the "normal" installation messages.

I removed the "source.inc" from the cck-directory of the buzzmonitor-module and the other content-types are now installed.

Tried to import the content type "source" with CCK Import. The following error message will be displayed after import: "An illegal choice has been detected. Please contact the site administrator."

So that is the error I had also in my installation screenshot in #5.

I tried also to import the content type "source" on an other drupal install, but the error stays the same.

I grabbed the "source.inc" directly from buzzmonitor-module from cvs and imported it in my installed site and now the content type "source" is available and I can start adding topics and get results.

The solution in #8 fixed the problem from me. I grabbed source.inc from CVS, did the install, and all the content types were created successfully.

That's weird. source.inc from buzzmonitor module v6-2.0 and in tar.gz should be identical.

Did you use source.inc from 6-2.0 or 6-1.0?

Thank you.

I used the version 6-1.0 Revision 1.1 of source.inc from buzzmonitor module.

@lennart,

which Linux distribution is this running on?

Same error here attempting to install Tattler.

O/S Ubuntu 8.04 LTS
MySQL database 5.0.51a
PHP 5.2.11-0.dotdeb.1

I have about a dozen other Drupal 6, Drupal 7 and an OpenPublish site all running on this same server without issue.

Will do some more testing but wanted to add version specifics to this issue since we are running into the same error.

Thanks. Can't wait to get Tattler running.

Thank you much!

We've been testing mostly on CentOS. Will get an Ubuntu setup up and test on that, see if that gives us any leads.

Thank you!

#12 above worked for me also. Version 1.0 beta of the buzzmonitor sources.inc content type imported fine. There are huge differences between the 1.0 and 2.0 versions of buzzword.

I'm getting the same thing. When I go to /node/add/topic it just shows Add Feed and Add Page. How can I fix this?

Just as a point of information, the exact same issue happens on CentOS 5.3. And it seems to start working after checking out the CVS versions of the buzzmonitor 1 files and installing instead of the distributed version.

While we have an idea about where the problem may be coming from, alas, despite our best efforts, we were not able to re-produce the problem. For that reason, we are trying to fix it in dark and hoping for your assistance.

if you had previously experienced the problem reported here, can you, please, try to install updated distribution from:
http://tattlerapp.com/sites/default/files/releases/tattler-1.0RC1-155.ta...

and let us know if the problem persists?

Sorry for the trouble and we _really_ appreciate your assistance.

Thank you.

tattler-1.0RC1-155.tar.gz looks like it's corrupted (I'm unpacking a single, unusable file -- unnnamed.dat)

tattler-1.0RC1-155.zip provides me with the necessary files, but upon re-install, I'm getting the same issue -- the "mention" content type isn't being created.

---

Many apologies.

Looks like I posted incorrect link in my previous message.

Updated distributions are at:
Tar.gz: http://tattlerapp.com/sites/default/files/releases/tattler-1.0RC1-156.ta...
zip: http://tattlerapp.com/sites/default/files/releases/tattler-1.0RC1-156.zip

Sorry for that and if you can try those, that would be fantastic.

Thank you!

The installation error described in #5 seems to have been fixed in 1.0RC1-156. Clicking on "trends" generates the following error:

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ) AND ( FROM_UNIXTIME(node.created) > DATE_SUB(NOW(),INTERVAL 7 DAY) ) G' at line 6 query: SELECT count(tn.vid) as mentions, t.name, t.tid, t.vid, t.name FROM term_node tn JOIN node node ON node.vid=tn.vid JOIN term_data t ON tn.tid=t.tid WHERE ( node.type='mention' ) AND ( tn.tid IN () ) AND ( FROM_UNIXTIME(node.created) > DATE_SUB(NOW(),INTERVAL 7 DAY) ) GROUP BY (tn.tid) ORDER BY mentions desc LIMIT 5 in /home/tattler/public_html/sites/all/modules/tattlerapp/tattler_trends/tattler_trends.module on line 121.

#614626 is a duplicate of this issue.

Okay build 156 installed without a problem and I am not receiving any errors when viewing trends. So far so good.

O/S Ubuntu 8.04 LTS
MySQL database 5.0.51a
PHP 5.2.11-0.dotdeb.1

This build seems to have resolved the problems we were encountering on the above platform.

The best news I've heard today :)

Thank you so much for helping us test!

I need one more confirmation from somebody else and we will push out new release.

Thanks, everybody!

I can confirm. New release solved my problem. "Topic" content type is now being created.

rhel5

PHP 5.2.6

MySQL 5.0.67

Although I should mention: .zip worked for me perfectly, but the .tar did not. (Though it could just be me.)

Thank you, guys, really appreciate your help with testing. Especially since we could not reproduce the problem.

@CrookedNumber,

what program are you using to unpack tar.gz? What operating system? Or if you use command-line, can you, please provide the exact command you tried?

Thank you!

No luck using the unarchiver (http://wakaba.c3.cx/s/apps/unarchiver.html) on leopard on a macbook pro. From the command line, however, everything worked fine.

[FYI: just Tried some other tar.gz files -- e.g., Drupal -- using the same GUI and it worked fine.]