I wish I had known that drupal exposes webform results by default, and how to clear google quickview caching

It should be a condition of download for Drupal that users acknowledge that they must not collect sensitive information in webforms without a lot of prior preparation because it will be published publicly on their site. I wish I had known.

I have a drupal 6 site (which uses tcpdf) for which I discovered that one of my webforms, which was collecting personal information, did not have the "viewable by anonymous users" permission revoked for "access all webform results". Never occurred to me to even check that would be default behavior for an input form submission, that the submissions themselves would even have configurable permissions. Drupal was making lists of webform results, and the results themselves, viewable by default. Therefore, google indexed the webform submission lists, the submissions themselves, and then took the pdf versions, converted them to quickviews and cached everything. A user notified us that their submitted information was available in google search results.

We revoked anonymous access to those drupal nodes, deleted the data from the server, and installed webform_nosave and I thought the cache would expire naturally. But a user brought it to my attention a couple weeks later that their data was still cached and viewable.

Current node's author as argument?

I am creating a block using views, I have it set on a page and want it to show related content of a specific type by the same author of the currently viewed node. anyone know how I can do this? I'm trying to do it in the arguments area. is this possible?

Help to hide Replacement patterns for title field of a content type

Hi,
I have a content type. This content type can be created by anonymous users. The content type has title, and a text cck field. I have a module to generate automatically the field title using a tokens, so I can hide the title for the creators of a node.

In the configuration of that content type I have selected: "Automatically generate the title and hide the title field" I have written the token I wanted to use to generate automatically the title.

Theming a 10 page section w/in a given site

Just wondered if there really is a 'best practice' when it comes to theming a certain section of a website entirely different from the main site.

Creating a new theme for that section complete with its own template files, using Panels Everywhere or something else?

I haven't quite got whether using Panels Everywhere actually needs panels everywhere (throughout an entire site) to allow for different themes within or if just a 10 page section could use Panels/Everywhere that overrides the main theme.

I found this after a search:

HTTP error 0 upon simple module update

OK, this relates to a simple Update, *not* a version Upgrade, but this seemed to be the best place to post it.

I have a site running Drupal 6.28. I've maintained it with few issues for several years. The only noteworthy feature it has is CiviCRM, which is uses a separate MySQL database anyway.

Yesterday, while attempting to make two routine module updates (the latest versions of IMCE and Views Bulk Operations), I received the following error message upon running Update.php:

An unrecoverable error has occurred. You can find the error message below. It is advised to copy it to the clipboard for reference.
Please continue to the error page

An HTTP error 0 occurred. http://www.justice4michigan.org/update.php?id=64&op=do

When I do continue to the error page, I receive the following details:

warning: array_pop() expects parameter 1 to be array, boolean given in /home/justice4michigan/public_html/update.php on line 316.

The update process was aborted prematurely while running update # in .module. All errors have been logged. You may need to check the watchdog database table manually.

When I check the error log itself, it just shows the same error as above. When I go back to view the status/updates available, it *appears* that everything has been properly updated.

writing to the accesslog table

Hi all...

Looking for a little help. I'm using views_pdf to generate a downloadable PDF for my users. A call to the PDF view does not generate any rows in the accesslog table. Is there a Drupal function I can use to write to the accesslog? Or do I need to build an INSERT SQL statement manually in a hook?

Pages

Subscribe with RSS Subscribe to RSS - Drupal 6.x