Wrong inline filter weight or order?
| Project: | Inline |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Hi, I'm having a weird behaviour with inline filter.
This is the situation:
- In my site I use inline filter for images.
- For general purpose -emoticons, style changes, etc...- I use Custom filter wich is based in Regular Expressions "language".
I'd like to render picture captions at the bottom of them. So, I need to catch the tags title="this is the title" and width="xxx" from html'd inline images. The process should be simple:
- Convert [inline:file=title] to proper html code with inline filter.
- Catch the required tags with custom filter and manipulate them.
So I set up the filter's weight to inline=1 and custom filter=10. Just for testing purposes and to ensure the regular expression used in custom filter is right I'm just trying to transform "alt" (without quotation marks) from < img src="..." alt="..." ... into "foo".
And here is the problem, nothing changes. As I said, I use custom filter for other tasks and it works right so I assume there is any kind of weight problem with inline filter.
Does anybody has information or suggestion about this issue?
Kind regards.

#1
Inline 1.x is not really an input filter, but runs in nodeapi('view') instead. hook_nodeapi() implementations are invoked in the order of module weights defined in the system table.
#2
Automatically closed -- issue fixed for 2 weeks with no activity.