I have tried checking and unchecking the boxes in Themes>Configure>Global Settings and the post information does not appear for Pages and does appear for Stories regardless of this setting. I have checked the theme's template.php and node.php files to see if they were overriding this setting and that doesn't seem to be the case.

Please forgive me if this is not an Acquia Prosper issue. However when I switch to Garland the post information acts as expected (that is, it observes the Global Settings).

I would be most grateful if someone could point me in the right direction!

Comments

jeremycaldwell’s picture

jeremycaldwell CreditAttribution: jeremycaldwell commented
Assigned: Unassigned » sociotech
sociotech’s picture

sociotech CreditAttribution: sociotech commented
Status: Active » Postponed (maintainer needs more info)

ozish,

I tested the Display Post Information global settings for Pages, Stories, and a variety of other content types while using Acquia Prosper on a local system. In every case I was able to add and remove the displayed post information.

Do you have caching turned on? If so, try clearing cache (under admin/settings/performance).

Have you modified Acquia Prosper's node.tpl.php or have you created additional node templates (e.g., node-story.tpl.php)? If so, has the "submitted" code or markup been changed from the default Acquia Prosper?

If you could provide additional information about any changes you've made to the theme or site configuration, or any contrib modules you've added that might alter the display of nodes, that would be helpful.

Thanks.

ozish’s picture

ozish CreditAttribution: ozish commented

Hi sociotech,

Thank you for the reply. I do hope that it's not something silly I've done, but at this point I don't think that's the case. Caching is off. I haven't done any theming yet - it's virtually a clean install.

To test I have done the following (on WAMP running on my PC - PHP 5.2.11, Apache 2.2.11, MySQL 5.1.36)

I have done a clean install of Drupal 6.15.
Create modules and themes directories under /sites/all.
Install acquia_prosper and fusion.
Enable acquia_prosper and fusion core and set a_p as default.
Create a content item of type "story".
Check front page to see that post information is there.
Go to global theme configuration to turn off "story" post information setting.
Go back to front page and post information is still there.
Switch default theme to Garland.
Front page - post information is gone.
Delete content item.
Install and enable skinr module (oops).
Switch default theme to Prosper
Re-create content item.
Front page - post information is there.
Check that post information is turned off in configuration - yes.
Check caching turned off - yes.
Clear cached data.
Clear browser storage (Firefox 3.5.5).
Check front page - post information is still there.
Switch default theme to Garland.
Front page - post information is gone.

The only problem I can see is that I forgot to enable Skinr before creating my first content item.

Please let me know if you would like me to do anything different, or to check anything on this clean install.

sociotech’s picture

sociotech CreditAttribution: sociotech commented

ozish,

Not enabling Skinr first shouldn't be an issue for this problem.

Have you tried any other contrib themes? Do they display/hide post information correctly?

The only other thing I can think of is to try the theme in another, non-WAMP, Drupal environment. I'm not familiar with the WAMP setup so I'm not sure if it does something different.

Sorry, but this is just baffling.

ozish’s picture

ozish CreditAttribution: ozish commented

OK I downloaded fresh versions of prosper and fusion 6.x-1.0-beta3 for both, since I didn't mention that earlier.

I noticed the problem initially on my (unix-based) hosting account. That installation does have other modules installed but it's basically a sandbox for me in terms of Drupal.

If you wish I can set it up on a domain I'm not using, see if I get the problem, and then if I do I can pm you with access so you can take a look.

But if I'm the only one with the problem that would indicate that it's local, or perhaps no one else cares about this. In either case it might not be worth your time. I can create a node template to get around it.

sociotech’s picture

sociotech CreditAttribution: sociotech commented

ozish,

If you could replicate it on a domain I could access that would be very helpful. Once you get it set up let me know and I'll take a look.

ozish’s picture

ozish CreditAttribution: ozish commented

OK just setting up now. One thing I noticed on setup was that I had to supply an .htaccess file to get clean URLs. I'm ashamed to admit that I don't remember where I picked up the one I'm using, but I don't see how that could be the problem. I'll reproduce it here just in case. There should be a PM coming your way within the hour. Thanks!

ozish’s picture

ozish CreditAttribution: ozish commented
Assigned: sociotech » ozish
Status: Postponed (maintainer needs more info) » Active

Temporary workaround:

  1. At admin/build/themes/settings under Username, disable the Display "not verified" for unregistered usernames setting.
  2. Save Configuration.
  3. The Display "not verified" for unregistered usernames setting can then be re-enabled if desired.

Post settings should then work properly after step 2 above.

ozish’s picture

ozish CreditAttribution: ozish commented
Version: 6.x-1.0-beta3 » 6.x-1.0-beta4
WorldFallz’s picture

WorldFallz CreditAttribution: WorldFallz commented

FYI - This also fixed acquia_marina beta 1 ignoring the 'submitted by' global setting.