Has anyone else had problems accessing the TinyMCE editor after upgrading from 4.7 to 5.1? After the upgrade we has several issues requiring a good bit of repair/rework. Once we got through that we found the text editor simply does not appear in the edit mode. We have uninstalled and reinstalled, deleted and changed the profile, logged out and in, etc. but to no avail.
I have recently been asked to administer a Drupal site for one of my clients. Have worked with lots of web sites, content managers, etc. but this is my first experience with Drupal. The site is currently using 4.7. The site is getting lots of bot posts to a form that is emailed for publication orders, and apparently there is a captcha module that might help. The client wants to include a graphic on the page that requires the user to read the characters and type them in. It does not need to be a rotating image, just a feature that will stop most of the bots from posting.
Hi,
I upgraded a full site from drupal 4.7 to 5.1.
I make full use of cck and views.
All went well except for this message while updating the database after cck was updated:
# user warning: Table 'xmysite-drupal.cache_content' doesn't exist query: SELECT data, created, headers, expire FROM cache_content WHERE cid = 'content_type_info' in /big/dom/xmysite/www/includes/database.mysql.inc on line 172.
# user warning: Table 'xmysite-drupal.cache_content' doesn't exist query: LOCK TABLES cache_content WRITE in /big/dom/xmysite/www/includes/database.mysql.inc on line 172.
# user warning: Table 'xmysite-drupal.cache_content' doesn't exist query: UPDATE cache_content SET data = 'a:4:{s:11:\"field types\";a:5:{s:13:\"nodereference\";a:3:{s:5:\"label\";s:14:\"Node Reference\";s:6:\"module\";s:13:\"nodereference\";s:10:\"formatters\";a:2:{s:7:\"default\";a:3:{s:5:\"label\";s:7:\"Default\";s:11:\"field types\";a:1:{i:0;s:13:\"nodereference\";}s:6:\"module\";s:13:\"nodereference\";}s:5:\"plain\";a:3:{s:5:\"label\";s:10:\"Plain text\";s:11:\"field types\";a:1:{i:0;s:13:\"nodereference\";}s:6:\"module\";s:13:\"nodereference\";}}}s:14:\"number_integer\";a:3:{s:5:\"label\";s:7:\"Integer\";s:6:\"module\";s:6:\"number\";s:10:\"formatters\";a:5:{s:7:\"default\";a:3:{s:5:\"label\";s:4:\"9999\&quo in /big/dom/xmysite/www/includes/database.mysql.inc on line 172.
I've just run a painful upgrade from a 4.7 Drupal installation to a 5.1. It's been a nightmare and it's still not over, because when I thought I was done (2 days' worth of work!) the Views module gave up.
I have views configured correctly (one shows a block, others are page views). I know their configuration is good in Drupal because the data is filtered and the resulting nodes/fields are displayed.
But... the views .css files that Drupal 5 wants separate from the main style.css are not processed anymore!
They are in the right position, in the root dir with their corresponding .tpl.php file. But Drupal/Views acts if they're just not there!
Opening the url of a page view and looking at the html, I copied the .css address in the import command and opened it in the browser: the .css file was immediately found!
It is worth mentioning that only the block view imports and uses its .css file as supposed to be. Why the block yes and the page views no?
I know this other blow to my mental sanity is related to the Drupal upgrade because I worked on views and css's right before the upgrade.
I already tried upgrading the Views module to the last version, and uninstalling/reinstalling the module.
I'm getting ready to upgrade from 4.6.10 so I did an rsync of all the files in the drupal web directory to a new system. Also did the same for the g2data files. I dumped the mysql db via mysqldump utility and reloaded it into the db on the new system. I changed the drupal and gallery configs to point to the new locations and adjusted user/pw/paths.