Extension talk:EmailPage

Guidance on CSS
Love this extension and I'm sorry to have to ask such a simple question, but as installed, my class="wikitable" css for tables is not finding it's way to the emailed html. Is this the way it is supposed to be? or is this indicative of an issue on my particular implementation? .. either way, please help me understand what I should do to get my default "Mediawiki:Common.css" CSS included with the emailing. Thanks! ~ User:revansx

Fill wgEmailPageContactsCat with a valid category doesn't show a drop-down list
The category contains subcategory that contains page with email adress

Thanks


 * Sorry, I did not see this before. See this section. Basically this configuration parameter is gone. --&#91;&#91;kgh&#93;&#93; (talk) 18:23, 9 April 2016 (UTC)

PHPMailer class not found!
The current download bundle doesn't seem to work, I get this error PHPMailer class not found! I tried setting $wgPhpMailerClass = "$IP/extensions/EmailPage/PHPMailer_5.2.4/class.phpmailer.php"; Also linked PHPMailer_5.2.4 to phpmailer in the extension dir and copyed it to /usr/share/php. I'm also seeing this in my apache error log PHP Notice: Undefined variable: dir in /home/txeng/mediawiki-1.26.0/extensions/EmailPage/EmailPage_body.php on line 13  Thanks. --Kc5vcx (talk) 03:26, 12 December 2015 (UTC)
 * Sorry, I did not see this before. This issue was reported and fixed at GitHub. You should give the new version 2.4.1 an shot. Cheers --&#91;&#91;kgh&#93;&#93; (talk) 18:26, 9 April 2016 (UTC)

Can't seem to get $wgEmailPageContactsCat to work
Hi, I have been experimenting with this extension and I have managed to get it to work and send emails, but I do not seem to be able to get the $wgEmailPageContactsCat option to work. I am using version 2.4.1, 2016-04-07

I have had a look at the code and I can see how the email page is built, but the page does not seem to be doing anything with $wgEmailPageContactsCat that I have noticed so I am not sure how to debug the process.

What format should the value be?
 * $wgEmailPageContactsCat = 'Catname'; OR
 * $wgEmailPageContactsCat = 'Catergory:Catname'; OR
 * $wgEmailPageContactsCat = 'Catergory:Catname';

When it comes to the subcategories do they only appear if the pages belonging to the subcategory have emails defined? Should this process be able to work with "User:username" pages that are added to the subcategory? Does the email value have to be defined in a template using or does it just parse the first email address on the page?

Also, when emailing a page, is it possible to just email a linkable title instead of the full page?

This option could be very useful for one of my current projects so it would be great to know.

Thanks --Jpadfield (talk) 17:53, 9 April 2016 (UTC)


 * I did not know that this configuration parameter existed. Well, it is indeed in the docu but I just looked at the code and saw that this parameter is no longer there, so it will not work in any case. Cannot tell why and when this was removed though. Cheers --&#91;&#91;kgh&#93;&#93; (talk) 18:01, 9 April 2016 (UTC)


 * Thanks for letting me know, it would have been useful, I will now explore using the API to create new user groups instead. --Jpadfield (talk) 21:16, 9 April 2016 (UTC)


 * Just to say, in case it is of use, if one is using Semantic Mediawiki it is possible to add email from pages listed under a category using an inline "ask" query, a bit like the code below, added to the send function in SpecialEmailPage.php, instead of the section that adds user emails from the media wiki groups. Where "Mbox" is the property for the email addresses:

$ot = $wgParser->parse("",  Title::newFromText('Email List'), new ParserOptions); $test = strip_tags($ot->getText); $elist = explode(",", $test); foreach ($elist as $k => $v) {$this->addRecipient( trim($v) );}


 * To Make the drop down in the first place I also added the following code to the execute function in SpecialEmailPage.php, instead of the section that creates the wiki group drop down. The getCategories function is just a simple list at the moment as I have not worked out how to list subcategories without calling the API.

$groups = " "; $cats = $this->getCategories ; foreach ($cats as $k => $group) {   $selected = $group == $this->group ? ' selected' : ''; $groups .= "$group "; }

--Jpadfield (talk) 12:55, 11 April 2016 (UTC)

PHPMailer security issue CVE-2016-10033
Exploits are in the wild for this security issue with PHPMailer. PHPMailer 5.2.18 resolves the issue. -71.36.99.196 00:37, 28 December 2016 (UTC)


 * Thanks a lot for notifying! Aran has released a new version of this extension this day. However an new critical is around so we need another release soon. --&#91;&#91;kgh&#93;&#93; (talk) 19:03, 3 January 2017 (UTC) Edit: reported here

#info: code not rendering in html emails
Hi.. Great extension, thank you!

I am using version 2.4.4, 2017-04-26 of this extension ith my MW-1.28.2..

I use the #info: tag extensively in many pages I wish to be emailed by users.. as it is now, these info tags get decomposed as inline text. Is there an easy way to allow them to be emailed as clickable info bubbles as they are in my pages?

For example, in tables, I have a column called "Title" where the content of the rows in that column are all of the patern:

... ... and in the email, it gets rendered as if I coded it like this: ... ... as you can see, the info tag wrapper has been removed. -User:revansx
 * TitleID
 * Some Short Title
 * Other Data
 * Other Data
 * TitleID
 * Some Short Title A very lengthy and wordy description...
 * Other Data
 * Other Data
 * You should mention that the #info parser function is provided by Semantic MediaWiki. This parser function was overhauled for the upcoming version 3.0.0. I will install this extension on sandbox smw to allow testing if there is also an issue with it now. Cheers --&#91;&#91;kgh&#93;&#93; (talk) 15:20, 11 December 2017 (UTC)


 * As reality has it there was another issue which I had to address on the server before testing this. The test shows that also in SMW the "info" parser function is changed to plain text representation in html. Admittedly I only use this extension for basic pages without any fancy stuff on it. Thus I did not encounter this issue. However, the elements rendered by "info" have deticated classes so it should be possible to do display none for them via a CSS page just for sending out content. Cheers --&#91;&#91;kgh&#93;&#93; (talk) 23:20, 12 December 2017 (UTC)