I've just found a little problem/bug...a recent feed item has some code that breaks the entire site/page. Really breaks it bad.

I've discovered, I can't just delete the item/clipping. I guess I would have to delete all of the clippings up to today which would be all of them.

I think, right next to HIGHLIGHT (this clipping), could be a very useful option - DELETE (this clipping). Only viewable, of course, to admins.

until resolution...

Can I delete the clipping from the database? Say the whole line of ID number 2456 or whatever, or will that cause a problem/break with the d3pipes programing?

I tried eliminating some data from the database entry data field, but that killed my site.

thanks.

After clipping, add a joint of reassign - striptags.

Anyway, I'll add an option to delete/ignore an entry.

I've installed a copy of .56a and happen to be looking around for the "delete this clipping option" for another clipping that really needed to be trashed. I believe the option was to be next to the Highlight this clipping option on the individual clipping page, but it's not there.

Has this idea been implemented yet? Or am I missing something?

Thanks.

n

Nevermind - found it - must have been a cache or template issue...much thanks for this option. It is very useful. Thanks.

n

GIJOE,

I've had another "problem" entry and tried to delete it.

Main clipping page:

Highlight it
_MD_D3PIPES_LABEL_VISIBLECLIPPING
_MD_D3PIPES_LABEL_DELETECLIPPING

This (above) is what shows for the selection boxes.

On a test site it will show:

Highlight it
Display this clipping
Delete this clipping

but since it only shows to admin, I didn't care...as long as it worked.

But deleting doesn't work. I deleted the clipping and it comes right back to it. Thinking it was in cache, I checked the database and that clipping is still there. And Did it again...same thing.

I could delete the clipping from the database, but that screwed it up last time.

Is there some kind of version problem going on? - cause all the versions are labeled .5 and there is no way to tell what version it is from docs/files inside the module.

I've got .56a files running and did a module update.

A "files changed" in the changelog would possibly help in the frequent upgrading of this module. Especially regarding templates that get customized.

Thanks.

n

Looks like this may be an "upgrade" issue. I've noticed that at least the templates are not upgrading.

A .54 install upgraded to .56a still has the same old .54 database default templates.

Even though the module update says it has created a bunch of (new) templates - they don't appear to make it to the database.

This explains why much is not working and the delete and visible options not even showing up.

n

adding to above:

3 of the "new" templates don't show up in any template set:

main_cliplist
main_xmlrpc2extendedping
main_xmlrpc2ping

Same with test site - So, upgrading not working.

How to fix the mess it's in now?

here's the upgrade output:
***************************************************
Module data updated.
Option's values of the block List entries (Async) will be kept. (value = jobs|138139521946c3468ca66bb|1,2,3,4,5|60|db:jobs_block_async.html|mergesort)
Option's values of the block List entries (Sync) will be kept. (value = jobs|7249770646e4243b00253|12,1,2,11,4,5|60|db:jobs_block_sync_big.html|separated)
Rebuilding blocks...
Block List entries (Async) updated. Block ID: 115
Block List entries (Sync) updated. Block ID: 116
Deleting module config options...
Config data deleted from the database. Config ID: 908
Config data deleted from the database. Config ID: 909
Config data deleted from the database. Config ID: 910
Config data deleted from the database. Config ID: 911
Config data deleted from the database. Config ID: 912
Config data deleted from the database. Config ID: 913
Config data deleted from the database. Config ID: 914
Config data deleted from the database. Config ID: 915
Config data deleted from the database. Config ID: 916
Config data deleted from the database. Config ID: 917
Config data deleted from the database. Config ID: 918
Config data deleted from the database. Config ID: 919
Config data deleted from the database. Config ID: 920
Config data deleted from the database. Config ID: 921
Config data deleted from the database. Config ID: 922
Config data deleted from the database. Config ID: 923
Config data deleted from the database. Config ID: 924
Config data deleted from the database. Config ID: 925
Adding module config data...
Config index_total added to the database.
Config index_each added to the database.
Config entries_per_eachpipe added to the database.
Config removeclips_by_fetched added to the database.
Config internal_encoding added to the database.
Config fetch_cache_life_time added to the database.
Config redirect_warning added to the database.
Config snoopy_proxy_host added to the database.
Config snoopy_proxy_port added to the database.
Config snoopy_proxy_user added to the database.
Config snoopy_proxy_pass added to the database.
Config snoopy_curl_path added to the database.
Config tidy_path added to the database.
Config xsltproc_path added to the database.
Config css_uri added to the database.
Config images_dir added to the database.
Config comment_dirname added to the database.
Config comment_forum_id added to the database.
Template jobs_admin_cache.html added to the database. (ID: 1035)
Template jobs_admin_clipping.html added to the database. (ID: 1036)
Template jobs_admin_joint.html added to the database. (ID: 1037)
Template jobs_admin_pipe_edit.html added to the database. (ID: 1038)
Template jobs_admin_pipe_list.html added to the database. (ID: 1039)
Template jobs_admin_wizard_fetch.html added to the database. (ID: 1040)
Template jobs_admin_wizard_inner.html added to the database. (ID: 1041)
Template jobs_blockedit_async.html added to the database. (ID: 1042)
Template jobs_block_async.html added to the database. (ID: 1043)
Template jobs_block_sync.html added to the database. (ID: 1044)
Template jobs_block_sync_big.html added to the database. (ID: 1045)
Template jobs_inc_entries.html added to the database. (ID: 1046)
Template jobs_independent_atom.html added to the database. (ID: 1047)
Template jobs_independent_rss10.html added to the database. (ID: 1048)
Template jobs_independent_rss20.html added to the database. (ID: 1049)
Template jobs_main.css added to the database. (ID: 1050)
Template jobs_main_clipping.html added to the database. (ID: 1051)
Template jobs_main_eachpipe.html added to the database. (ID: 1052)
Template jobs_main_index.html added to the database. (ID: 1053)
Template jobs_main_jsbackend.html added to the database. (ID: 1054)
xoops_module_update_jobs executed successfully.

Module Jobs updated successfully.
********************************************************

It's not using, nor can I access templates with those ID's in the 1000 range. It's "stuck" with the old templates.

I tried uploading the new template files manually, but that doesn't seem like a good solution - considering I can't get the new (listed above) templates added.

And speaking of those 3, they are not listed as being "added" by the module upgrade output listing.

Gee - one badly formed entry and all hell breaks loose...at least on my site...

n

Quote:If you use the core of xoops.org's version, fix the bug.
And clear templates_c/