I saw your other post.
I don’t see how it could be related to the modified Easy Newsletter module as it only retrieves the existing web user data.
Sounds like it might possibly be related to Sessions.
If you want to PM me a link & login I could have a quick look.
I cant seem to get this to work. After uploading/replacing files, Im having difficulties even getting the backend module to display correctly. When I click into the module all I see are three small blue boxes???
Anyone help?
bS
Maybe something wrong with the module configuration or paths?
Difficult to say without having a look inside the Manager.
Can I PM you details for manager?
Yes, I’ll have a quick look and see if it’s anything obvious.
Hallo! Tried installing your code after the 0.3 version. Got an error @ the backend:
Warning: include(../assets/modules/easynewsletter/languages/.php) [function.include]: failed to open stream: ��� ������ ����� ��� �������� in /home/users1/m/mmice/domains/tclub.biz/manager/processors/execute_module.processor.php(114) : eval()’d code on line 76
Warning: include() [function.include]: Failed opening ’../assets/modules/easynewsletter/languages/.php’ for inclusion (include_path=’.:/usr/local/zend/share/pear:/home/users1/m/mmice/domains/tclub.biz/manager/includes/’) in /home/users1/m/mmice/domains/tclub.biz/manager/processors/execute_module.processor.php(114) : eval()’d code on line 76
and the dame for the line 30.
What am i doing wrong?
Thank u
Oh, that helped!
But now it’s a problem while trying to sent broadcast^
« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« Execution of a query to the database failed - Table ’mmice_modx1.modx_web_user_attributes’ doesn’t exist »
SQL: SELECT * FROM `modx_web_user_attributes` WHERE `blocked` = 0
[Copy SQL to ClipBoard]
Parser timing
MySQL: 0.0012 s (4 Requests)
PHP: 1289995273.5142 s
Total: 1289995273.5155 s
ah! i see.. i have a "modx1_" prefix, that’s the problem.
shall try to find the place where i have to make a fix..
Fixed, it works! Thank you!
P.S. One question: is there any way to use users name in the letter? Smth like "Dear %name%! We are..."?
Not easily the way it was originally written.
I suppose it would be possible to have a placeholder like [+name+] in the newsletter template.
Then do a replace with user name value from the DB on each send.
