Extension talk:HTMLets
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Not working with PHP 5.3.x | 6 | 00:58, 30 November 2011 |
| Mix with mediawiki code. | 1 | 07:05, 9 October 2011 |
| Subfolders? | 0 | 07:04, 9 October 2011 |
| Trouble relocating the htmlets directory | 4 | 07:01, 9 October 2011 |
| Does this work with 1.12? | 2 | 06:58, 9 October 2011 |
| Does this extension need "$wgRawHtml=true"? | 2 | 06:56, 9 October 2011 |
| ISO-8859-1 | 1 | 06:55, 9 October 2011 |
| PHP code support ? | 1 | 06:54, 9 October 2011 |
| Div Tags | 1 | 06:53, 9 October 2011 |
| Error in base64_decode text | 3 | 06:52, 9 October 2011 |
| Help | 3 | 06:50, 9 October 2011 |
| Iframe bug? | 0 | 06:49, 9 October 2011 |
When trying to use this extension with PHP 5.3.0, the following error occurs:
Warning: Parameter 3 to wfRenderHTMLet() expected to be a reference, value given in /.../w/includes/parser/Parser.php on line 3243
Any help would be appreciated. Thx
I can confirm that, I have exactly the same problem (line 3243) under PHP 5.3.1 now! So I have put away the Probably from the title. ;-)
PHP 5.3 seems to be quite picky here. Should be fixed in 1.17 67215.
Hello Daniel, with 1.17 you mean the next release of MediaWiki, correct?
After updating to XAMPP 1.7.7 with PHP 5.3.8 and MediaWiki 1.17.0 I again got the same problem, just on another line:
Warning: Parameter 3 to wfRenderHTMLet() expected to be a reference, value given in ...\includes\parser\Parser.php on line 3470
Then I downloaded the last version of the extension and replaced the previous version and added the necessary line ($wgHTMLetsDirectory = "$IP/htmlets";) to the LocalSettings.php and now it works fine again, at least for me!
Affirmative. After upgrade to PHP 5.3.8 this extension stopped working (same error message). (MW 1.17.0) I guess I will file a bug. Cheers
Edit: Done with bug 32714
It would be nice to add wiki code inside HTML pages, for example, autofill username in a form field.
HTMLets are for static HTML only. Extension:RawMsg might allow something like this, not sure.
In any case: pre-filling form fields with user-specific information has to be done with JavaScript anyway. Remember that the generated HTML for pages gets cached. This means that there can be no user-specific content there.
Is there any way to split HTMLet files into subfolders within the main htmlets directory?
I've got a lot of these and it would be nice to separate them, rather than having them all in one megafolder.
I tried
<htmlet>subfolder/filename</htmlet>
but that didn't work.
No biggie if this is impossible.
I've had the extension working with the htmlets directory located in the default location under the "wiki" directory. Wanted to move the htmlets directory to the root of my server so I can open up ftp directories without giving access to the htmlets directory. Entered the following in localsettings.php:
$wgHTMLetsDirectory = "http://localhost/htmlets/";
Used ?action=purge on the test page but still I get error message. Is there something very simple I'm overlooking (I'm new with all this stuff)?
Well, what do you mean by root - the file system root, or the document root? the URL above refers to the document root.
Anyway, unless you want to access htmlets on a different server, it's better to use an (absolute) file path instead of a URL, for example "/htmlets/" or some such. This would refer to the htmlets directory directly in the file system root.
Hi Duesentrieb, thanks for fast response - was not familiar with the localhost concept and did not find enough explanation when looking around. I guess I mean "the file system root" but "http://localhost/htmlets/" was what I got from your help text. Just tested again and still haven't solved it.
When localsettings.php has $wgHTMLetsDirectory = "$IP/htmlets"; I get the htmlets served ok from /public_html/wiki/htmlets
When localsettings.php has $wgHTMLetsDirectory = "/htmlets/"; I do not get htmlets served, neither when locating the htmlets-directory in the server root shown in my ftp-progam as /htmlets nor when locating it as /public_html/htmlets. I wonder if "root" is really "root" - I run the site hosted with Siteground (I see the locations the same way when checking through their web-based ftp interface).
Again, I'm not really familiar with server concepts, I might be doing something wrong. The file permissions are shown as the exact same for all three locations of the htmlets-directory (-rw-r--r--).
Any hints?
The "root" you get from your FTP program is probably not "the" filesystem root, but simply your home directory or somethign similar. Ask your host what the actual file path is.
Alternatively, you can do this: $wgHTMLetsDirectory = "$IP/../../htmlets"; that's "two up from where the wiki is, and then into the htmlets dir".
What I don't quite get is... you want to open ftp directories? but hopefully not in a why that would allow others to manipulate your wiki files. that would be kind of bad...
Great, thanks Duesentrieb. The "two up"-approach worked. No, I will open up ftp only for one or more external developers ... I need a little help, as you can gather ;-) and will soon be looking around for someone who'd be interested for pay.
Does this work with 1.12? Could you provide some more documentation on installation? I have installed many extensions, but I can't seem to get this one to work. Thanks
I have not tried on 1.12, but i don't see why it wouldn't work. But then, there's the new preprocessor code, maybe that itnerferes. WIll try to look into it in a couple of weeks. Installation should be streight forward, there's nothing special to do.
I figured my problem out. When I downloaded the files, I used the 'browse' link (http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/HTMLets/) which took me to the wrong versions of the files. It seemed to download 'log' files or something, and not the actual PHP extensions. Thanks
I am comparing Extension:SecureHTML with HTMLets. Not being a programmer I like the simplicity of this extension and I think that is all I need to include a javascript. Will this extension work even with "$wgRawHtml=false" or does that need a "true"?
It will work with $wgRawHtml=false; If you have that set to true, you can insert HTML anyway, so using this extension would be pretty pointless.
Thanks for clarifying this for a newbie, it wasn't quite clear on Manual:$wgRawHtml where I first found a link to this extension so I will make a small change there also ...
This is a great extension. But i have a problem with showing the html-files. I have HTML with charset ISO-8859-1 and when i use this htmlet then a char like é is displayed wrong (in Firefox 2). In IE6 it even stops showing the page. When i set the charset of the browser (which is standard on UTF8) to 8859-1 it goes allright... Does anyone knows what the problem is and how to solve it?
Mediawiki uses UTF-8 for everything. If you want to inline HTML-snippets, they need to be encoded as UTF-8 too. Or use character-references like &t;amul; etc for all non-ascii characters.
hi guys,
thanks for the great functionality this extension brings to Wiki.. really helpful ! got one question - i keep trying to have it parse PHP files as well - as far as i can see, when htmlet requests the file, the web server will return the results as HTML, so i don't see why it won't work...however it does not work...for me at least :) any help / hint is highly appreciated
ahh...figured it out myself... all you need to do is specify "http://" and the complete path to the php file, and the resulting HTML output will be rendered, rather than the PHP source ;)
Very useful, thanks a lot! I thought div was an allowed HTML tag in MediaWiki. Apparently it isn't. However, with HTMLets I can insert them where I need them.
Hey Dues, I found a bug in the base64 hack I originally sent you. To fix, change line 115 from this:
'/<!-- @HTMLetsHACK@ ([0-9a-zA-Z\\+]+=*) @HTMLetsHACK@ -->/esm',
To this:
'/<!-- @HTMLetsHACK@ ([0-9a-zA-Z\\+\\/]+=*) @HTMLetsHACK@ -->/esm',
I had forgotten that '/' is a legal base64 character.
Thanks - fixed in revision 19993
Thank you I am now going to create a form, and adapt the inputbox extension to take from that form and create a new page. Which will then give us the holy grail of a form creating a page and filling in a template
The above comment was posted anonymously. Does somebody know if the described 'holy grail' was actually created?
Can I use this to somehow load a Javascript apt into a mediawiki article? I'm trying to load the REVVER video JS into a mediawiki article. I'm just not sure how to go about doing that. Would I create an HTML file, put the JS in it, and save it in the HTMLets folder, with this extension installed? Thanks
What about javascript in the <html>?
what about it? it should work like it always does in html. Or are you reffering to using the <html> tag to inlude raw html inline on the wiki page? That only works if you have $wgRawHtml enabled. In which case using HTMLets is pointless.
When I try to use this with an Iframe, the iframe shows up but everything on the left side of the page (logo & sidebar) are gone.
