I belive that mod comes from the XOOPS France guys. You can try asking athttp://www.frxoops.org/ if you don't get a better answer here.

HTH,

tar/gzip is built-in to most UNIX/Linux systems. On windows I believe 7-zip can compress in this format.

Are the templates you are trying to upload in the correct format? Also, there is a particular structure (I believe) that the compressed archive must follow. I don't know what that is though, but a dev may be able to tell you or it may be in the FAQ.

HTH.

Hey Brash,

I appreciate very much all the work done by the XOOPS team or I wouldn't be here for so long. I started on PHP-nuke, realized it wasn't up to par and did a lot of research before settling on XOOPS as the best. It will take a long time to migrate my site, so I am jus trying to run in parallel for now and hoping this gets sorted out. I am going to try m0nty's new suggestion over the weekend and see if I can fix the remaining issues by emptying the additional tables. (after backing up!)

I understand being protective of the devs, but I also believe in being fair to all sides and not downplaying something based on what it may impact. I am not saying one is right and one is wrong, that is just how I operate. It may indeed ruffle feathers.

As for being vuln to Santy, I don't believe XOOPS was to the original worm which just did phpbb, but later variants attacked a more general PHP vuln/coding insecurity that we were. At least that is what I thought when I saw the patch come out shortly after it appeared (which is why I upgraded in the first place). Ironic if I upgraded for no reason.

As for the number of sites affected, I dunno. But I have a strong suspicion that many of the recent posts (and there have been many) of people reporting blocks disappearing, not updating, etc. are all related to this same issue. There is something awry with updating/installing modules and it impacting the blocks/templates. I think it remains in 2.0.9.2 as well, since I don't think everyone who is having issues with various blocks all upgraded to 2.0.9. Not 100% sure, just an educated feeling based on years of troubleshooting. Perhaps a dev knows if a change was made somewhere in the process that takes place when that module install/update icon is pushed.

As a side note, in my current state, my tempates aren't red anymore, but if I download my template set, and upload it, the links and system turn red. If I do the same with the default template set, wf-downloads turns red. Two different template sets, both not functioning 100%, but in different places. Perplexing. But my site is at least 90% working now. What is left that is broken is manageable for now and hopefully will get better after the "stage 2".

I will let you know how "stage 2" goes and how I make out. Thanks for helping out.

Quote:

I went through all your steps monty with some success, but more non-improvement (I think).

I now have:
1. A template set that does not appear in red in all the spots (good)
2. Blocks that still don't update (no improvement)
3. Blocks that still reverted to showing (empty or 0) for show XX number of posts, forcing me to go in and reset them to 10 so 3000+ comments don't show up on my pages (no improvement)
4. Still had duplicate blocks. However I went in to the DB, searched for the block titles (main menu, recent links) etc. and removed the dupes. So far they haven't reappeared as dupes, but they may. However, when doing this I noticed something that may help track this down. The dupes were identical in the DB, except for one field, BLOCK TYPE. For each dupe, there was a block with block type S (which I assume stands for system) and block type M. I deleted the block type M dupes. Perhaps this is a clue as to what is causing the bug. (no improvement but fixed manually).

So, I guess we have made a little progress. No idea what to try now. (Download a full 2.0.9.2 and do a mass replace via FTP for the whole site?)

Thank you for your help.

newbb2 has that. Each forum has a section at the bottom where you can tick to the off position "can post without approval" for registered users or whoever else you want to require pre-approval for.

HTH.

Wow, lot of stuff here. I guess this will be a long post.

Quote:
Tried/trying to do so.
Quote:
Doesn't fix, as DB is the issue once you upgrade. Also, leaaves you vulnerable to Santy worm.
Quote: Already done.

Quote: Not an option.
Quote:
What I am in process of doing since that's all that left.

2.0.7.3 has security issues so it isn't an option. It is the reason I upgraded, not becuase of PHP5 support.

Quote:
I don't know which group you are putting me in, but is it unreasonable for someone to expect the core team, when they make a release with a major bug, to then correct that mistake? Everyone makes mistakes. You do. I do. But I don't then go tell people to pound sand. I attempt to 1) apologize, 2) explain what happened 3) work to correct it. I find it astonishing that people think it is OK for the dev team to tell the user base to pound sand and go fix it themselves. If that is really the attitude, than XOOPS has bigger problems than this bug.

I would be happy to help the devs fix this, but there has been zero feedback on what to do. No: Can you try making change X in file Y.php. That makes it hard to fix for a non-coder. Or even for a coder who wasn't involved in the dev process for these upgrades.

My attitude isn't you broke it, you fix it.
It is you broke it, let's get this fixed.
But from the other side all that has been received is "we broke it. Sucks to be you (plural). We'll fix it when we get around to it."

Not good.

After the bug was discovered the dev team worked very hard to fix it so that other people weren't affected. There were a number of quickly released patched (2.0.9.1 and 2.0.9.2) to correct it so other people didn't get hosed. But then BOOM. Nothing. Can't be much of a priority if we can get immediate fixes out within a day, but have nothing happening for four weeks for those who got bitten by the bug.

jegelstaff is absolutely correct. This isn't a tiny little bug, but something that badly breaks a XOOPS site. If we were using a trouble-ticket system, it would be lableled "critical". Yet it sits unresolved, and worse yet, UNASSIGNED in the bug tracker. With little to no feedback from the devs on what, if anything, is being done to correct it.

So here is what I have done:
1. Tried rolling back to a previous version of code
2. Tried regenerating my templates
3. Tried regenerating my blocks
4. Tried cloning my template set
5. Tried downloading and then re-uploading my template set
6. Looked in the database for something that could be corrected. However the templating system spans a number of tables, making it beyond my ability to find anything helpful.
7. Filed a bug on sourceforge
8. Filed a bug here on XOOPS.org
9. Tried a different theme
10. Kicked self in ass for not backing up my DB before patching.

So without any feedback from the devs on what can be tried now, I really don't think there is anything else I can do. If you have a suggestion, I am all ears. If not, then I believe my time is better spent migrating to another CMS than it is banging my head against a wall trying to locate the source of this bug by randmomly firing off in every direction until I hit something.

PS - Conrats on your MVP award brash. It's a good program and alot of fun.
PPS - I don't think anyone else is saying "just fix it for me" either. I could be wrong though.

You can add me to the list of frustrated people. Actually, I think I am more frustrated than kiwiguy.

I appreciate very much all the hard work the devs do. I have shown my appreciation by giving back quite a bit I think (helping with docs, answering posts here, etc) with the little things us non-developers can do. But I can't understand how work is going on on new module released, etc., when a bug introduced by the team has farked over multiple XOOPS sites and goes unassigned in the bug tracker and appears to have had minimal work done on it despite being reported on XOOPS.org the very first day the upgrades were released (weeks now).

I believe this is related to your blocks/templates issue from the upgrade. I have the same issue with blocks not updating.

Once the templates/blocks problem is sorted out, it should be fixed.

PS - Add me to the list of people with duplicate blocks. I had "double main menus" showing up all over the place yesterday.

Replace favicon.ico file with one of your liking.

HTH.

Quote:

Tis in the FAQ:

https://xoops.org/modules/smartfaq/faq.php?faqid=9

HTH