Installed the TB Sirate Starter (tb_sirate_starter-7.x-1.0-beta2.zip)

Get the notice "Notice: Undefined index: drupal in update_requirements() (line 35 of /home/hildecjs/public_html/tb/modules/update/update.install'

Please advise action to correct.

CommentFileSizeAuthor
#7 tracking-issue.jpg112.47 KBwilliampham
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hildesheim’s picture

Title: Notice: Undefined index: drupal in update_requirements() (line 35 of /home/hildecjs/public_html/tb/modules/update/update.install » Notice: Undefined index: drupal in update_requirements() (line 35 of /xx/xx/xx/tb/modules/update/update.install
drupalnz’s picture

- backup your db and website directory
- Download the latest drupal version, extract overwrite everything except the sites directory
- run db updates: /update.php

hildesheim’s picture

Hi drupalnz, Thanks for reply and suggested solution - unfortunately still get same notice.

williampham’s picture

The issue is caused by information added by drupal.org to every files .info during packaging process:

; Information added by drupal.org packaging script on 2013-05-29
version = "7.x-1.0-beta2"
core = "7.x"
project = "tb_sirate_starter"
datestamp = "1369825864"

Almost every distributions has this issue. There is a quick fix to solve this issue:

  • Go to your tb sirate starter source code /modules/update/
  • Open the file update.info
  • Remove the information added by drupal.org
  • Clear Drupal cache

Moreover, new version of TB Sirate Starter 7.x-1.0-beta2 has been released. This release comes with TB Mega Menu, an innovative and user-friendly module to create flexible mega menus. Be the first person to check out this cool module and give us your feedback to improve it.

chrysonline’s picture

Hi,

just the same thing if you want to install the great "Administration Menu" module (https://drupal.org/project/Admin_Menu)

Go to your module/system and delete the information added by Drupal.org in system.info (or add : version = "7.22" instead of 7.x-1.0-beta2...)

kifuzzy’s picture

Hi :)

surfing web, drinking coffee i downloaded a version (beta3) installing on a win-sys with xampp / vhosts.
update the core, ok so far.

but - run updates i see it needs a librarie version 2. .

maybee you make an update of this inst.profile .. if i remember it correct it was a dependency on awsome fonts? (edit: and the vimeo-video-iframe.. or an advice about google-analytics)

however whatever, second thing i saw was not liking that somewhere in sites is google analytics activated. dont know what code or which number, or whatever - i will have one more cup of coffee to have a look where this googlecode is in instprofile´s data after creating fresh.

first look .. tracker via embedded vimeo video file. (google-analytics)

tracking installations this way?

it´s via the embedded video in structure/blocks .. the demo video in TB Mega Menu.
changing the iframe or content for this part of in or disabling .. however

i do not like to be tracked without asking or advice.
something like "when you install / use then we .."

otherwise:
really nice work.

williampham’s picture

FileSize
112.47 KB

Hi kifuzzy,

Google Analytic tracking code is not from us. It comes from vimeo.com service. Actually, The block "Demo Video", which is used in the mega menu, is a custom block. It has an iframe tag to retrieve video content from VIMEO service and the tracker is inside the iframe. It means the tracker belong to vimeo.com service, not us. You should a look at the below picture:

Tracking Issue

kifuzzy’s picture

Hi,

thank your for detailed and fast reply :)

had a closer look to files later to get info about to whom the analytics belongs to.
but - could´nt you use another demo-player-video/version inclduing in it, could you? in a way that browsers and user not getting "hmmm" when have a first look to fresh install of it and see the message "google-analytics" on.

newbie_drupal’s picture

Thanks to #4 WilliamPham! The same issue exists in TB Purity Starter. I had been experiencing this issue for months and no one could resolve it. Thanks for the fix, my message doesn't appear anymore.

Igbonine’s picture

Just Saving,

hoekbrwr’s picture

Issue summary: View changes

Now I am trying to install beta5 and I get this error again. Sorry that I do not understand all of the above, but if this is a problem from drupal.org why not mend this???
How to clear cache in Drupal, I am rather new to drupal!?
OK I upgraded manually to 7.28 and now I am rid off that problem. Now I get a warning/advise to add some .htaccess files to 2 folders, but the remedy is upgrading to at least 7.24 and I am now on 7.28??? What to do?