I wish I had seen your post before I posted the following in the news article announcing the release of 2.0.18.1rc:

Quote:

Another good argument for using the search function...

I had the issue with all browsers.

Actually, with a little adaptation, the sitemap module does work with Google Sitemaps. Mine was read by Googlebot 15 hours ago. It creates xml_google.php for you, which Googlebot reads. IT does also give a list of the various pages, module by module on your site (which you can control via preferences).

For whatever reason, it seemed I struggled with getting it working, though, for a while. The sitemap protocol was a little confusing to me.

Having written that, your recent posts have been very helpful and creative.

I use the sitemap module from here. It does take a little adaptation but it serves my purposes pretty well. It would be nice if a standardized approach was adopted more as part of the core, however.

I too have been here a long while. I come here much less frequently now. It's too painful. I have been looking around trying to find other ways to manage my site.

In life and in this place, I wish we could show the politicians the door. The reality is that kind and respectful people don't want to spend time in the kind of environment that we have tolerated here.

So, until those who have called folks idiots, have used abusive language (acronyms), or whatever other forms of abuse apologize and move on, nothing will improve.

Similarly, those who routinely bait these discussions should be banned. Isn't it interesting how these folks always advocate for these discussions being held in the open? Right. They enjoy the controversy. They like being the center of attention.

I have nearly decided that there is no will here - in spite of some good advances - to deal with building a respectful community. Until that occurs, from the top down, we will continue to revisit this sorry discussion.

By the way, I don't always understand some of the posts that I read from some of the folks who say they don't speak English well. But, I respect you and the work you have been and are doing for xoops. I read your posts and I like what many of you are saying... Some of you are the reason I have stayed as long as I have.

I just saw your post here.

I suspect that this use of page wrap is the answer to both problems. I am not at all familiar with pagewrap, but I suspect that it is also the issue with the module not found issue as well. If you have several of these modules and they are not configured in some special way, perhaps it may be that XOOPS is not recognizing them and therefore is also not showing the appropriate icons. It sounds like there were some other folks in that thread who knew what they were doing with that mod so it may be helpful to f/u with them, as well.

Good luck. Wish I could have helped.

What version XOOPS are you using?

I don't know if pageWrap plays nice with the current version. I don't believe it does, but not sure. Perhaps someone else knows.

Also, you may want to try this re: the admin menu: delete everything in templates_c except index.html and see what happens.

Issue 1:

Try this. Go into the cache directory and delete everything but index.html. Make sure and delete adminmenu.php. When you then go into your admin pages, your site will regenerate the adminmenu.php. IT will indicate that you have not been into the admin home page before because it is regenerating the menu data before. MAKE SURE YOU BACK UP BEFORE DOING THIS...

Issue 2:

I suspect you uninstalled the module but you have one of several possible issues: In a module directory you have incomplete module files for the given module or you have only the module directory name with no files. The page load will show that error in module admin if you have module directories with incomplete module files, no files, or incorrect files for that given module. You can bank on it. Sometimes, when that error has occurred, it is because I inadvertently uploaded some of the module files to an incorrect module, or uploaded some of the module files without actually putting them into a directory.

How to fix?

Review each directory in ROOT/MODULES to make sure that only the files unique to each module are in that directory, that there are no files themselves at all in the ROOT/MODULES directory except index.html, and that the files in each directory only pertain that that module.

HTH

Quote:

A rather wide-ranging post... Not really so much about templates_c after all, it seems.

I wonder what that means?

For myself, I like the morpho themes and use them. My site visitors find them more attractive, easily used, and accessible. They do require some extra attention and skills. But, in my opinion, they're worth it. If you don't like them, that's fine. If you don't like templates_c. That's fine too. You gave your reasoning.

Quote:

But, you still managed to. I read this thread because I thought I might learn something. There's this strange sense, though, that it's more about complaining. So, I guess I'll move on to a thread where people have something to ask/say/really contribute.

A couple of ideas:

First, I would consider uninstalling/removing xcgallery and then clearing the cache and templates_c directories (leave index.html in htem). Then, update the system module. Then, see if you still have your error.

Some themes, in my experience, don't play nicely with xcgallery.

In general, any time I make changes to blocks, etc. I clear the cache and templates_c directories - as noted above - before I leave the site because that's the best way to see if the changes are what you really wanted.

I hope this helps. I saw that you posted in the Beginner's Corner so I hope this doesn't sound too pedantic. Occasionally some snippy people feel like their being patronized. No intent here to do that.

Just wanted to jump in here. This may, or may not help.

BUt, script_fu, you note that that is your mainfile.php. Is that the mainfile.php after your install or before?

After the install, it will not have the values you are noting in your previous reproduction of your mainfile.php:



The installation process edits the uploaded mainfile.php with the values that are unique to YOUR site. If - during the upgrade process - you replace the mainfile.php with the one from the package, you will kill your previous install.

The mainfile.php that you showed us previously is the stock mainfile.php that is intended to be overwritten. That is the reason that you set mainfile.php to have permissions 777 during the install process: so that the install process CAN overwrite mainfile.php.

Now, if you upgraded from an earlier install, and you uploaded and thereby overwrote the mainfile.php that was modified during the initial install, then XOOPS will simply not work.

Due to inattentiveness when upgrading, I have - on a number of occasions - overwritten my mainfile.php only to have similar kinds of headaches. Moreover, if you did overwrite it, you would need to set all the unique values in mainfile.php to the values unique to YOUR site. The values included in the file you posted are NOT going to be valid for your site.

What else leads me to wonder if this is what happened? Because of the following statement:

Quote:

Your mainfile.php (the one that you will have after your installation) will NOT be the same as the one in any of the packages. It will have different values.

Course of action IF I am correct?

1) Make certain mainfile.php is set with permissions at 777

2) Make sure the mainfile.php on your site reflects your sites unique values (eg. it will almost certainly not say the XOOPS_ROOT_PATH is /home/mydomain/public_html). Change the other values as well.

3) Reset Mainfile.php to 444

Just trying to help. I could be full of crap. But don't think I am. At least, that's what I would check...