Problems with input formats

Hmmm it's probably my passing the row contents back through check_markup when re-submitting rows... I guess... I'll look into it tomorrow...

Can you just let me know a couple of things though to help with re-producing this error;

• Which input filter you're using?
• What filters you have enabled for that input filter (and what order they're in)
• Whether you have a rich text editor enabled for single line input (and which one it is, fckeditor, tinymce, etc)
• What the stored serialized row 'looks' like actually in the database both before and after the problem occurs.

That'd be great thanks.

...And I'm afraid it's infeasible for me to integrate CCK fields into Tablemanager, they're completely different things - the code would have to be ultra complex to compensate for the differences in what the two modules are trying to achieve and I'm afraid I'm just not clever enough to be able to do it... On the plus side though, Tablemanager v2 'borrows' *cough* a whole lot of code/ ideas from cck and views to make compatibility maybe a little easier for someone who knows their way around CCK better than I do. Which I don't... At all... Bah...

As I've not released any code at all for Tablemanager v2 here's a little snippet about it;

Tables are now created as nodes and like CCK creates content types as new individual tables in your database, so does Tablemanager. It'll make creating custom sql display queries a whole lot easier than the serialized arrays Tablemanager works with now. There's a new set of pluggable modules (in the same way Tablemanager v1.5 for Drupal 6.x has) which include a query builder like Views 2.x, so non-coders will be able to create complex sql queries without knowing anything about sql (okay so I'm having a lot of trouble with this, but it's in the pipeline). ...Blah, blah, blah - I snipped that from another post - I've written quite a lot in previous issues about v2 of Tablemanager so please refer to them for more info on the changes in functionality!

Pobster

Hi pobster,

> Which input filter you're using?

Default input format: PEAR Wiki Filter

> What filters you have enabled for that input filter (and what order they're in)

-9 Footnotes Textile style
-7 Amazon filter
-6 Code filter
0 PEAR Wiki Filter
2 Tablemanager filter
10 Zeilenumbruchkonverter (line brak converter)

> Whether you have a rich text editor enabled for single line input (and which one it is, fckeditor, tinymce, etc)

No, none at all. What for, I have Wikitags ;)

> What the stored serialized row 'looks' like actually in the database both before and after the problem occurs.

Before:

After saving once:

I hope this helps.

Thanks & greetings, -asb

PS: The idea about CCK fields as table manage data types was not supposed to be a serious suggestion (even I'd be some kind of cool ;)

Ah excellent I don't need to install Drupal 5.x I can see quite clearly what's happening here... I'm passing the entry through the filter and *then* storing it in the database. I thought that was what you're supposed to do... Pass user input through Drupals filter system to make sure that it's not doing anything naughty and then store it... Of course... Doing that is converting your link [http://drupal.org/drupal-5.5 Drupal 5.5] actually into what it's supposed to represent; <a href="http://drupal.org/drupal-5.5">Drupal-5.5</a> and then it's storing it in the database. When you edit it, rather than give you back this; [http://drupal.org/drupal-5.5 Drupal 5.5] you're getting the link and your html input filter obviously isn't set to accept links. Now this is a problem... As I really don't know what I'm supposed to do here? I think I'm going to need to take some advice... Obviously I can't just store whatever the user inputs unchecked and then pass it through the filter only when it's displayed, as anything which is stored in the database needs checking for malicious input. Hmmm... I'll get back to you on this...

Pobster