Hi,
So I just installed the module, but I can't figure out how to get it to work the way it's supposed to.
At first, I tried installing and it threw the site into an error. I refreshed, and saw that the module had been enabled anyway, but I couldn't find any site of it on the site. To resolve that issue, I had to disable, uninstall and clear the cache, then try re-installing again before it occured to me to check the Newsletter blocks to see the Real Name field (I really feel this should have been documented somewhere).
Okay fine, the real Name field is on the Newsletter block but that's the only sign I see of it. It's not showing up in my tokens, and when I add a subscriber there's no realname in the subscriber list. Heck there isn't even a column for it. I read in the instructions that the RealName module wasn't 100% necessary (the site I'm using it on will only ever have on registered user: me) but I decided to install it anyway. Nothing. Still no sign of the Real Name token. Did I do something wrong?
| Comment | File | Size | Author |
|---|---|---|---|
| #25 | simplenews_realname-1912712-25.patch | 15.79 KB | sgabe |
| #21 | simplenews_realname-1912712-21.patch | 14.87 KB | deggertsen |
| #16 | simplenews_realname.patch.txt | 14.45 KB | emilorol |
| #10 | simplenews_realname.patch.txt | 13.61 KB | emilorol |
| #8 | simplenews_realname.patch.zip | 3.65 KB | emilorol |
Comments
Comment #1
Ony commentedComment #2
heyehren commentedYes, i have exactly the same issues that you've described. I get the following error:
Comment #3
emilorol commentedHi,
The error is generated when the module try to load the name field for an anonymous user and since the anonymous user does not have an email define the error is printed. Here is a solution:
Locate the function "simplenews_realname_form_alter(&$form, $form_state, $form_id)" and in a new line after global $user; add
Comment #4
emilorol commentedHi,
I was also getting the error:
and I was able to fix it by doing this:
1. Locate function "_simplenews_realname_get_realname($mail)"
2. Find:
3. Replace:
That should be all.
Comment #5
emilorol commentedHi,
My last 3 bugs of the day:
The reason for this issue is the use of:
That code was good and valid for Drupal 6, but it does not work in Drupal 7. The fix is simple:
Find:
Replace:
I know a patch file with all the mention issues will be good, but I don't have access to shell right now.
Comment #6
emilorol commentedHi (again),
I got one more little bug when the user try to subscribe from the subscription block and the module try to replace the token in the outgoing email.
The reason for this bug is that in the function "simplenews_realname_mail_alter(&$message)" there is check to see if "$message['body']" is an array and when test TRUE it calls:
The solution is simple since $message['body'] is an array of strings, find the above line and replace it with:
One more bug down.
Comment #7
emilorol commentedOne more to keep it intresting:
Error:
Find:
Replace:
Comment #8
emilorol commentedHi,
Here is a patch with the latest correction to the module. A lot of the issues had to do with the changes in DB and Field API from D6 to D7. The only thing I didn't had time to change was the export features so that you can export the name with the email address.
Thank you.
Comment #9
heyehren commentedAwesome emilacosta! This fixed the issue for me! Thank you very much.
Comment #10
emilorol commentedHi,
Here is the latest version of the patch with a couple more bugs fix for the subscription block.
One thing that is not included in this patch is the fix for the install file mention here: http://drupal.org/node/1894202
As for the TODOs:
1. Creation and re-use of helper functions for operations that repeat over and over like subscribe, unsubscribe
2. Ability for the user and/or admin to edit a name after registration in form: admin/people/simplenews/users/edit/-->UID
3. Map the realname field to any profile field without using the "Real Name" module
4. Hopefully one day make it an entity that can be fielded (a better solution than http://drupal.org/node/127178)
Thank you,
Emil
Comment #11
heyehren commentedWhen i try to bulk import a list of users i get the following error:
I'll try your new patch later and see if this will fix the issue.
Comment #12
emilorol commentedHi,
Try applying the latest patch and clean your cache, so far when I go to: http://mysite.com/admin/people/simplenews/import to import address it works for me.
A couple of tips:
1. Only 1 name and 1 email per line (NAME LAST;EMAIL@ACCOUNT.COM)
Example:
2. Since you are using the realname module the import has to have the name and the email and if there is no name you still have to put the semicolon (;) in front of the email
Example:
3. Don't forget to select the newsletter otherwise there will be no subscription action.
To add to the previews TODOs List:
1. Make the subscription selection required (maybe this should be done by simplenews itself)
2. Improve error handeling to let the user know what it wrong with the data he/she is trying to import
3. Import from a CSV file or Feeds
Thank you.
Comment #13
heyehren commentedI still can't get it working on my website, but i applied the patch to a fresh Drupal installation and there it works.
I have tried the following steps on my website:
- disable the simplenews and simplenews realname modules
- uninstall the simplenews and simplenews realname modules
- removed the remaining simplenews tables in the database (field_data_field_simplenews_term and field_revision_field_simplenews_term), although they didn't have any content anyway)
-cleared the cache
-activated the simplenews and simplenews realname modules
I've tried all of this with both the dev and the recommended release of the simplenews and simplenews realname modules (including your latest patch).
I still get the error when trying to mass subscribe:
Could this be related to another module that i have installed? Or a remaining database entry that hasn't been removed during the uninstall?
Comment #14
heyehren commentedstrangely i still couldn't find the root of this issue. But i found a few more hints. Any help would be greatly appreciated.
I found out that even though i get the non-object error message (http://drupal.org/node/1912712#comment-7100014), the name and email address is still added in the database table. but for some reason it doesn't show in the subscriber list.
And i have deactivated almost all modules on my test site, but the error still occurs, so it might not even be a compadibility issue with another module?!
Comment #15
jw100 commentedI'm seeing exactly the same error as kleinermann in #13 when trying to mass subscribe.
Ditto for the database table updates in #14.
We've also done the same version testing as kleinermann, and always receive the error.
Has anyone found a solution to this import problem? Any input would be greatly appreciated!
Comment #16
emilorol commentedThis patch should make the error go away.
Comment #17
jw100 commentedThank you emilacosta and wow! Your new patch has fixed the import error.
I'm very interested to know what you changed in the patch?
Again, thanks for your time, effort and community contribution!
Comment #18
emilorol commentedYou are welcome jw100, I am glad to know the patch worked for you.
The change if I remember correctly was due to a change in how the taxonomy term is handle to connect the user with the right newsletter.
Comment #19
Ronni-1 commentedI had the same issues in the mass subscribe. The patch solved that issue. But there are a few more problems -
When i go to the Newsletter Subscriptions page and i hit next at the bottom of the page for the next subscribers, it still shows me the first set. The bottom menu changes from page 1 to 2 but the display is still showing the first 30 subscribers.
And when i Export all subscribers then only the email ids are shown comma separated. There are no names.
Comment #20
deggertsen commentedThere are lots of problems with this module right now in D7. #16 is a huge step in the right direction in my opinion. I had started debugging and had made many of the same changes found in the patch in #16 before I found this issue and simply used that patch. With it, the module appears to be at least mostly working. The patch fixes a whole slew of incorrect variables, and random bug fixes that appear all over the place when the dev version is first installed.
This issue has become a bit of a mess, as it covers a whole slew of issues. I propose that the patch in #16 be committed to the dev branch and that this issue be closed and any other specific issues can then be opened separately. I have opened one specifically for token issues: #2018487: Integrate with Tokens instead of using text replacement method. A separate issue should probably be opened for #19.
Whether the patch in #16 is perfect or not I really can't say, but it's makes the module a whole lot more stable than it was before the patch. This is why I think it should simply be committed and then we can go from there. Obviously I am not the maintainer though so we will have to wait and see what @sgabe says.
Comment #21
deggertsen commentedI decided to reroll the patch so that it's not a .txt file. Not that it matters too much...
Comment #22
cehfisher commentedI added the patch in #21 to the dev version and it seemed to make the module work. I am doing further testing now, but I was able to add an anonymous user to the newsletter subscription list. Thanks!
Comment #23
jjmackow commentedI also added patch #21 to the latest dev version and removed the
Notice: Trying to get property of non-object in _simplenews_realname_get_realname()
error message; and the module functions as described with the patch.
Nice work folks! thankyou.
Comment #24
jjmackow commentedI also added patch #21 to the latest dev version and removed the
Notice: Trying to get property of non-object in _simplenews_realname_get_realname()
error message; and the module functions as described with the patch.
Nice work folks! thankyou.
Comment #25
sgabe commentedCommitted, thanks!
Comment #27
nofue commentedI installed this module only two days ago and the initial error message (from the original post) still appeared.
I applied the fixe from #3 and the problem was gone.
Trying to subscribe an anonymous user gave me the same issue as described in #6.
Applying the fix suggested by emilorol (thxs for your support) worked for me as well.
Now the module doesn't issue any messages at least (testing still pending) but I strongly suggest that these fixes are also applied to the module as it was obviously overlooked when posting #25 …
Addition: Seems things are fine with the .dev version. So by all means, commit the .dev to alpha2 or whatever pleases you to help non-programmers to get things done.
Thanks you.
Comment #28
nofue commentedComment #29
kreatil commentedClosing this issue again, since the current dev version seems to work for @nofue, so it does for me on a Drupal 7.41 installation with Simplenews 7.x-1.1+1-dev and Simplenews Realname 7.x-1.0-alpha2+1-dev