Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options
vLaTeX
vLaTeX
0
Comments
2. put vLaTeX 0.1 into extensions folder
3. activated vLaTeX in admin panel
4. changed lines 146 and 147 in default.php according the astacey's comment above
result: 2^2 gets parsed to $$2^2$$
Am I missing something?
When you say "2^2 gets parsed to $$2^2$$", are there some missing tags there? Depending on how much of vLaTeX is working I would expect you to see one of three things:
$$2^2$$ stays as it is
$$2^2$$ becomes 2^2
$$2^2$$ becomes a picture of what it ought to be
From what you say, it seems as though the first one is happening, am I right? In which case it shouldn't be an issue with the text formatter but looks as though vLaTeX isn't even getting called. I'm sure this isn't the case, but you did select the right tags in the configuration panel, didn't you? And did you do the steps to create the cache?
I'll try it on 1.1.9 and report back, but in the meantime please try the other tag options and see if they work, and please tell me which text formatter(s) you are using.
Thanks
$$2^2$$ becomes >vlatex<2^2>/vlatex<
In testing, though, I discovered one or two things that maybe weren't so clear from the documentation.
The simplest way to get it working is to use the standard formatter and make the change indicated above. I should probably change these around so that it works out-of-the-box with the standard formatter and the change needs to be made for other formatters. Next time that something more serious needs updating then I'll do that.
If you want to use it with another formatter, then you need to do a little configuring. I tend to use the Markdown filter. On a live forum where I have this working, then I've disabled Markdown's HTML sanitiser, choosing to use KSES instead. The problem is that the vanilla Markdown addon cleans out ALL tags (if you look at markdown.php you'll see that the wordpress implementation is a little more sophisticated: it has a whitelist to which one could add vlatex if one wanted). The Markdown change in the readme merely tells Markdown to ignore the contents of the vlatex tags, which is necessary but is a second step.
Perhaps I should have chosen something else as the internal tags than fake HTML tags. However, it made a sort of sense: you don't want markdown (or any other filter) looking inside the latex code and it's usually fairly easy to tell a filter to ignore text inside certain HTML tags as they generally have a system already for that. Also, you don't want the user putting in the internal tags without meaning to, and someone typing any HTML tags, real or fake, is going to be fully aware what they are doing. But it does mean that the sanitisers have to be a little more clever than simply removing all tags.
That said, it doesn't answer kaikajus's problem. I can't see anything wrong in what you said you did, but you didn't list all the necessary steps to get this addon to work so I can't tell if maybe you just missed one out or just didn't say that you did it. Specifically, you didn't mention setting up the cache. And you didn't mention changing the tags from the default \[\] to double dollars $$ $$.
If your installation isn't an unusual one, the URL for the cache should be:
http://hostname/path/to/vanilla/extensions/vLaTeX/cache
The key bit is the last three components: "extensions/vLaTeX/cache"