After I upgraded from 7.14 to 7.15, this module didn't work anymore.

I can't create new snapshots - instead I get this:
Warning: fopen(): Filename cannot be empty in demo_set_info() (line 580 of /var/aegir/platforms/drupal-7.15/sites/all/modules/demo/demo.admin.inc).

---
Drupal 7.15
Access to update.php Protected
CTools CSS Cache Exists
Colorbox plugin 1.3.19.3
Configuration file Protected
Cron maintenance tasks Last run 16 min 52 sec ago
Database system MySQL, MariaDB, or equivalent
Database system version 5.1.49-3
Database updates Up to date
File system Writable (public download method)
GD library rotate and desaturate effects 2.0
PHP 5.3.3-7+squeeze8 (more information)
PHP extensions Enabled
PHP memory limit 128M
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Update notifications Enabled
Upload progress Enabled (PECL uploadprogress)
Web server Apache/2.2.16 (Debian)

Comments

ladyofthelake’s picture

Anyone? Any thoughts what might be causing this...?

walpio’s picture

I am experiencing this also.

Anonymous’s picture

I just had the unfortunate experience of the demo module completely erasing my site (all database tables except watchdog were dropped) when I tried to reset it. Not sure what went wrong. I was using latest version of Drupal 7.x and latest version of the demo module. Site was still under development and now I will have to start all over. Kicking myself for not making any real backups of the database first, but the demo module has always worked in the past.

Anonymous’s picture

To follow up on my issue, again I'm not sure how it happened, but the Table Definitions weren't added to the .sql file. Instead of

--
-- Table structure for table 'views_display'
--

CREATE TABLE IF NOT EXISTS `views_display` (
  `vid` int(10) unsigned NOT NULL DEFAULT '0' COMMENT 'The view this display is attached to.',
  `id` varchar(64) NOT NULL DEFAULT '' COMMENT 'An identifier for this display; usually generated from the display_plugin, so should be something like page or page_1 or block_2, etc.',
  `display_title` varchar(64) NOT NULL DEFAULT '' COMMENT 'The title of the display, viewable by the administrator.',
  `display_plugin` varchar(64) NOT NULL DEFAULT '' COMMENT 'The type of the display. Usually page, block or embed, but is pluggable so may be other things.',
  `position` int(11) DEFAULT '0' COMMENT 'The order in which this display is loaded.',
  `display_options` longtext COMMENT 'A serialized array of options for this display; it contains options that are generally only pertinent to that display plugin type.',
  PRIMARY KEY (`vid`,`id`),
  KEY `vid` (`vid`,`position`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci COMMENT='Stores information about each display attached to a view.';

It had:

--
-- Table structure for table 'views_display'
--

 ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci COMMENT='Stores information about each display attached to a view.';

What I did was reinstall Drupal from scratch, enable all of the modules as before, create all of the fields as before, then made a new snapshot (this one was made correctly - I checked). I then ran WinMerge on the two sql files (the old, broken one that had all of the data but no table definitions, and the new one that had no data but still had table definitions). After a lengthy merge, I was able to 'repair' the old broken sql file and get it to use that in the Reset for the demo module, which got my site back to a mostly working state. A couple hours and lots of stress, but in the end, demo module seems to working fine now. I'm using the dev version now though, so not sure if the problem with 7.15 is still there or not. Just let this be a warning to people to make real backups of the database from time to time!

Matthijs’s picture

A separate issue has been opened for the missing table definitions: #1795792: SQL dump files include partial table definitions.

Matthijs

brianhinkley’s picture

I had the same problem with getting the error

Warning: fopen(): Filename cannot be empty in demo_set_info() (line 580 of...

The solution that worked for me was to set my parameters for public, private, and temp directory under >> admin/config/media/file-system menu item.

What finally fixed my error was that I needed to create the temp directory. The default is /tmp. The directory can be created outside of the Drupal directory. This will help to eliminate the possibility of accidentally deleting it during an upgrade to Drupal core.

gaurav.kapoor’s picture

Issue summary: View changes

I am using 7.56 and latest dev is working fine.Some of the other commits might have resolved this issue.

gaurav.kapoor’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.