image is not being displayed anymore
Dragolin - August 24, 2009 - 19:06
| Project: | Inline |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I just updated the module and now my image is not being displayed anymore, instead the [inline]-tag is the output ??
I haven't changed my code at all, I'm using: [inline_upload|file=Oog van Horus.jpg|title=Oog van Horus]
Did the way to input the images change? I didn't read anything in the latest readme.txt or the release note ??

#1
I did not update but startet just today looking onto this module (Inline 6.x-2.x-dev (2009-Aug-12)) and get the same: the inline syntax as described in the Readme does not seem to work. Yes, the input format is set to use the inline filter.
Auto-inlining of attachments does work.
#2
I just installed this module and I had the same problem. I took a peek at the code, and it looks like the syntax changed to:
[upload|file=x]#3
Yup, the syntax in the readme and the CURRENT readme on the module page is totally out of step with the syntx in the actual module file.
Needs updating on the webpage I reckon.....
Here's the bit from the module: This syntax worked for me-----
You may link to files uploaded with the current node using special tags. The tags will be replaced by the corresponding files. For example:
Suppose you uploaded three files (in this order):
[inline:1=test] or [inline:imag1.png=test]
will be replaced by
<img src=imag1.png alt=test>[file:1=test] or [file:imag1.png=test]
will be replaced by
<a href=imag1.png>test</a>[attachment:2=test] or [attachment:file1.pdf=test]
will be replaced by
<a href=file1.pdf.png>test</a>#4
Hm doen't seems to work at all as Bensbury proposed.
#5
Having the same problem.
Suggestion in #3 is wrong, this syntax is for version 1.x of inline module.
In my own tests I found the same solution as #2, so this might be the intermediate buggy syntax.
On quickly reading the module files I couldn't figure out how the module works and which hooks are called. There seems to be a mix between old and new style. I could not find, where syntax is implemented.
#6
There maybe different ways of doing this but if the suggestion in #3 is 'wrong', how come it works and the others don't.
For my set up, solution #2 failed.
So #3 maybe well be the old syntax, but the old syntax works and the information on the webpage and documentation didn't.