Zen-based Drupal template for BYU's MPAA
PHP JavaScript Ruby
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
css Added Disqus; removed old CSS for comments and forums Aug 28, 2011
images
js
templates
.gitignore
.rsync
README.txt
Rakefile
block-caucus_index.tpl.php
block-footer.tpl.php
block-highlight.tpl.php
block-navigation.tpl.php
block-page_closure.tpl.php
block.tpl.php
box.tpl.php
ckeditor.config.js
ckeditor.styles.js
comment-wrapper.tpl.php
comment.tpl.php
favicon.ico
forum-icon.tpl.php
logo.png
mpaa.info
node-caucus_topic.tpl.php
node.tpl.php
page.tpl.php
region-page-closure.tpl.php
region-sidebar.tpl.php
region.tpl.php
screenshot.png
template.php
theme-settings.php
user-login.tpl.php
user-profile.tpl.php
user-register.tpl.php
views-view--front-highlight.tpl.php
views-view-fields--caucus-index--block-1.tpl.php
views-view-fields--caucus-index--block-2.tpl.php
views-view-fields--caucus-index.tpl.php
views-view-fields--front-highlight--block.tpl.php

README.txt

# Hacks/modifications to enabled modules

## Feeds

When Feeds runs with Poor Man's Cron, feed update messages will be displayed to all users. So, if an anonymous user happens to visit the page right after a feed update, they'll get a lot of technical, behind the scenes information. 

Unfortunately, the maintainers of Poor Man's Cron and Feeds are in a deadlock over deciding who's module is at fault, so this probably won't get updated in the near future. (http://drupal.org/node/867054)

To fix this, I patched `feeds/plugins/FeedsFeedNodeProcessor.inc`, wrapping the following code (around lines 46-56)

	if ($batch->created) {
		drupal_set_message(…);
	} elseif {
		…
	} else {
		…
	}

with a simple test to check if the user has permission to administer feeds:

	if(user_access("administer feeds")) {
		// drupal_set_message stuff from above
	}