I have activated, and configurated my simple news block so users can subscribe to a newsletter from it.

I have made the SN block visible for all users.

However as user #1 i am only able to see the block on the admin pages.
As soon as i visit website pages the Simple news block dissapears.
Permissions are set well.
And even if i list website pages in the SN block properties, the block won't appear.

I am running SN in combination with Domain access, thinking this was the problem but other blocks which i activate can be seen on all the pages within the domain.

Tried SN 1.0 and dev version as well.

Thanks.

Comments

fdambrosio’s picture

Same problem, I have Domain Access too

sutharsan’s picture

fdambrosio, if you expect a reply you need to spend more time to document your problem.

held69’s picture

As i was working on a non-production site i deinstalled simple news 6.x-1.0 and installed version 6.x-1.0-rc6.

After 6.x-1.0-rc6 i didn't have any problems, i configured SN and did an upgrade to 6.x-1.0.
All the setting remained and kept their functionality.

nb
During the upgrade (after update.php i did receive an warning message)

   * warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/mysite/domains/mysite.com/public_html/update.php on line 174.
    * warning: Invalid argument supplied for foreach() in /home/mysite/domains/mysite.com/public_html/update.php on line 338.
sutharsan’s picture

I have not used simplenews with domain access, or had any reports on it. can't be of much help on this.

sutharsan’s picture

Status: Active » Closed (fixed)

No activity, closing issue.

held69’s picture

Category: support » bug
Status: Closed (fixed) » Active

I have added a new newsletter and it looks that the problem shows up with each new block that i add.

As mentioned before, the block is displayed on admin pages however as user 1 i cant see the block on site pages.
Despite the block properties being marked as 'should display on all pages".

Tried simplenews 1.1 but didn't help.

Tried upgrading to dev version didn't help + got a user warning:
user warning: Unknown column 't.status' in 'where clause' query: SELECT COUNT(*) FROM simplenews_subscriptions s INNER JOIN simplenews_snid_tid t ON s.snid = t.snid WHERE s.mail = 'webmaster@mysite.com' AND t.tid = 12 AND t.status = 1 in C:\wamp\www\drupal\sites\all\modules\simplenews\simplenews.module on line 1204.

Thinking of downgrading to 6.x-1.0-rc6 again then.

sutharsan’s picture

Is this error due to Domain Access? Domain access is currently not supported. Please debug your system and supply code to change this.

held69’s picture

Project: Simplenews » Domain
Version: 6.x-1.x-dev » 6.x-2.4

Thanks for replying.

As i am not a coder i am unable to solve this with code myself.

Taking this to domain access

held69’s picture

Title: Subscription block only displayed on admin pages » Subscription Simplenews block only displayed on admin pages only icm with DA
agentrickard’s picture

Project: Domain » Simplenews
Version: 6.x-2.4 » 6.x-1.x-dev
Category: bug » support

I see nothing related to DA here, other than the coincidence of the module being installed.

DA is a node access module. If Simplenews doesn't support the Node Access API, that's a bug in Simplenews.

I assume that the Simplenews block is reading from a node. If that node is not visible on all domains, it makes sense that it would disappear.

Moving back.

held69’s picture

Status: Active » Fixed

After some more testing this bug seems more like a configuration matter of the domain taxonomy module.

I noticed that after creating a newsletter a taxonomy term in the 'newsletter vocabulary' is created.

With the domain taxonomy module i had to configure the taxonomy term so that it pointed out to the right domain.

After that the newsletter block showed up just fine.

Setting this to fixed for now

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

rookmoot’s picture

Indeed the problem is linked to the taxonomy module. Configuring terms or removing this module could corrige that problem.