cm starterkit difficult - message error

abdelrahman's picture

I'd like to use cm starter kit difficult, but when custom scheduling module sent error message :
strict warning: Only variables should be passed by reference in cm_airing_grid_get_grid_header() (line 138 of /Applications/MAMP/htdocs/cm_starterkit_difficult-7/profiles/cm_starterkit_difficult/modules/contrib-cm/cm_airing_grid/includes/
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'fdfasr.field_airing_show_ref_nid' in 'on clause': SELECT * from ( SELECT DISTINCT airing.airing_id
I don't know about this error

Comments is a great

kreynen's picture is a great place for general discussions, but specific issues should be opened in the distribution you are using or the specific module. In this case that would be or

But as stated on the DSK project page...

"Unlike the Easy and Moderate Starter Kits, the difficult kit is used more to communicate changes needed for the layer of customizations the stations building on top of it need."

The specific module throwing the error is only available as a development snapshot.

All of this isn't done to discourage you from using this code, but to give you a better idea of what will be expected of you or the developers you hire to get it to work. By sticking with the Moderate version of the Community Media Starter Kits (MSK) and only installing modules that are included in the DSK that have reached a beta release, you're less likely to run into issues like that.

The DSK currently includes code to integrate with Telvue, Cablecast, Morpheus and Cinegy playback system. What system are you trying to integrate with?

Really I'm trying to

abdelrahman's picture

Really I'm trying to customize DSK for build grid table , met data,reports so I need some modules to support me to manage my data because our station has just storage system so I need to tool to help me at my work

The Airing Grid is designed

kreynen's picture

The Airing Grid is designed to help with scheduling by providing a UI to visually see gaps in a schedule and create playlists Airings related to Shows that are exported as XML or pushed to an API of a playback server. While the information that is pushed to the server often includes the relative path to the file from the server that is going to handle the playback, creating forms and Views to collect and display metadata about Shows can be done with

You only need the DSK if you want the full CRM, Reservations, AND playback server integration. As it says on, "these are modules shared by large sites with staff who can support the more complicated configurations". The DSK is really more of a tool to track the versions that the largest/most self service oriented stations can work together. If you don't have a lot of Drupal experience or access to someone who does, this is not where you should be starting.