I might be misunderstanding you, but here's what I think...

Templates get 'installed' into the database whenever the module is installed or updated via the admin panel. If you've physically added a template file to your module's directory structure and have defined that template file in your xoops_version.php file, then you need to install/update that module from the system admin panel in order to get that template copied into your database.

Also, if you are using a non standard template set, you'll want to ensure that the template set you're using also has the latest copy of the smarty template too.

Hope this helps...

This probably won't help much...

You could try increasing the "memory_limit" in your php.ini file. Apparently, it's limited to 16 MB for any given page request.

I have to admit, though, 16 MB should probably be enough. My ISP for LankfordFamily.com has an 8 MB limit (I think), and I've never had a problem with it. If the code on your site has a real problem, then no amount of memory being thrown at it will fix it, so your mileage may very with this response!

Thank you both for your help. I'm much further along now!

Yes. All this should get you very close. But one thing that might drive you nuts is the fact that if you have lots of posted content, you might have lots of links (images, hyperlinks, etc) that were created in all that content that point to your URLs in their old location.

So if, for exmaple, your site were "http://www.i_am_cool.com/xoops", and you were moving it to "http://www.i_am_cool.com", then you might expect to find lots and lots of places where the "/xoops" part is hard coded in your database.

You can fix this though. Here is a sample script that you can save to your server's root directory and run once (after moving all your files) to correct this issue:



Of course, you'll need to fill in the details at the top of the script like user name, db name, password, etc. You'll also want to be sure to remove this script from your web server after you've run it!

Note: This script's operation is irreversible so be careful what you replace! If your replaceThis string is too vague, then you'll probably end up breaking a lot of things that you didn't mean to! For this reason, it's really important that you back up your database before running this script!

P.S. Bonus points for altering the script to show you what it will do before making it actually do it! That way you can sort of check to ensure that the 'hits' you're getting are the ones that you want to get.

Ok, so I'm a total noob on this TinyMCE thing.

As far as #1 above, turns out that there is a plugin for context menus. My first thought was that it was a config item passed in through the init settings. But that's not how right-click menus work at all in Tiny. Rather, TinyEditor supports the right click menu out the box. You just have to add that particular plug-in to your group's toolbar (duh).

So, slowly but surely, I'm getting there. I'm very impressed with TinyEditor and am so glad that others have gone through the effort to get all this up and running.

My only remaining question now is to figure out how to upgrade the TinyMCE inside of TinyEditor without causing havoc within the module. Still working...

It's no longer under development, but you could look at Xoops Gallery. I would recommend the 1.3.3.9 release.

This module is a "Xoopsified" version of Gallery.

I'll answer part of this myself.

It looks like you can just drop in plugins from TinyMCE without serious consequence. I've dropped in MCImageManager, MCFileManager, and Template without any problems.

So far, so good. I've also figured out how to get my XOOPS authenticator object (for MCImageManager) to start respecting some of the TinyEditor settings (like upload dir and user dirs).

More as I figure it out...

I've been messing around with TinyEditor for the past couple of days. I really like the idea of settling down on one specific WYSIWYG editor for my site. I have some questions about the module (version 1) and hope this gets to someone who's familiar with the code for it!

1) If I download TinyMCE and run the 'full featured example' with it. I get TinyMCE context menus whenever I right click. With TinyEditor, these right click menus do not appear. Rather, the context menus for the browser show up instead. Why is this? Is this a behavior I can change?

TinyMCE Right Click Menu:


TinyEditor Right Click Menu:


2) How easy is it to upgrade the TinyMCE code within the TinyEditor module? Do I have to wait for a new release of the module, or can I simply copy the new release of TinyMCE into the 'editor' sub-folder of the tinyeditor module? I guess I'm just wondering what the expectation here is. Are you meant to upgrade TinyMCE in this manner with TinyEditor?

3) I've noticed that there are available plug-ins that you can download from the repository for the TinyEditor project. Can I quickly and easily add plugins for TinyMCE (that maybe aren't present in the TinyEditor repository) by copying them into the appropriate directory structure on TinyEditor? Beyond setting up icons and such for the toolset management screens in TinyEditor, is there any other work under the hood being done with general TinyMCE plugins to make them compatible with TinyEditor?

I've purchased Moxicode's Imagemanager and Filemanager products and am going through the process of trying to integrage them with TinyEditor. The answers I get to the above questions will help me decide if I want to continue down this path, or 'hard-code' the standard TinyMCE install into my XOOPS site.

Thus far, I've managed to get the plugins into TinyEditor and have set up their icons in the toolset manager. I've created a XoopsAuthenticator class that correctly creates upload directories on a user-by-user basis for the image manager. So I am making some progress...

After I finish with this work, I do plan on posting here about the steps it takes to integrate MCIImageManager and MCIFileManager with XOOPS for others to save them some time...

Thanks in advance for any light that anyone can shed here!

Thanks for the reply.

I copied the file over a couple of days ago:



Since then, however, it's restarted 3 times on me. I didn't actually restart the server after copying the file over though. I'll do that real quick ... ok, I'm back.

I'll give it a shot again for a few days.

Thanks again for everyone's willingness to help. I may just be out of luck. My googling has brought me to the same conclusions that I'm seeing here: Apache + PHP + Windows = bad. I thought this stuff was more stable than that, and that I must be making a stupid mistake. But with all the bugs in the tracker and severe drought of any real leads to work on ... well, maybe I'm out of luck unless/until I install Ubuntu Server on the machine!

--------------
Do people have luck running XOOPS under IIS??

Biteronboard -- Thanks for the response.

I'm not maintaining multiple domains/hostnames on my server. Because of this, I'm not really well versed in the whole virtual host setup thing with Apache. So, what I'm saying here may end up sounding like unintelligible garbage .

The main Apache error log is where I'm going to get any error information. The entries in the log end up looking like this:

Quote:

Yes, there's some stuff in there about my SSL certificate not matching the server name. This doesn't appear to affect the SSL operation of the site, however. I've tried tracking this one down and couldn't quickly find anywhere where these values don't match. Irregardless, I don't think this has anything to do with the restart issue...