When I hold my mouse over a menu option, a yellow caption popup appears with the name of the menu option that the mouse pointer is currently over.

Is there a way to prevent the yellow caption popup from appearing? I don't see any settings in the preferences to turn it off. I assume that it is triggered by JavaScript code. I'm using MultiMenu 1.8.

Dave

Hi phppp,

I mistyped the version number. I apologize for that. I meant 3.01, not 3.1.

Thank you for the information. I will wait for 3.02

Dave

Hi jensclas,

I read the comments prior to initially posting here, which just put more questions in my mind. As you mentioned, there seems to be a lot of mixed reviews on 3.0 and 3.1. I was just wondering if I would be better off using an earlier version of CBB, or going with 3.1. It is difficult to determine that by just reviewing the comments on the bugs, since the comments tend to focus on specific bugs, rather than on the module stability as a whole.

I usually wouldn't be so concerned about this, but there are so many different versions of CBB that it has become kind of confusing.

Dave

Hi,

Which version of CBB is currently the most stable for a production environment? I see many versions, including 3.0 and 3.1. Is 3.1 the most stable and least buggy version?

I'm currently running XOOPS version 2.0.13.2. I've not yet installed any versions of CBB.

Dave

Hi adrock,

That fixed it! Thank you!

Dave

Hi,

I just upgraded from Multimenu 1.7 to 1.8., the 16 menu version. I'm receiving a bunch of errors, and I'm not sure if there is something I did wrong during the installation.

I overwrote the 1.7 module (all the files) with the new 1.8 module, and then updated the module in the administration section of my XOOPS installation. I noticed that there is an upgrade folder in the module, but the upgrade files in that folder seem to be for older versions (thus, I didn't run those).

Here are the errors I'm receiving:

Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_09 - assumed '_MI_MULTIMENU_NAME_09' in file modules/multiMenu/xoops_version.php line 336
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_10 - assumed '_MI_MULTIMENU_NAME_10' in file modules/multiMenu/xoops_version.php line 350
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_11 - assumed '_MI_MULTIMENU_NAME_11' in file modules/multiMenu/xoops_version.php line 364
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_12 - assumed '_MI_MULTIMENU_NAME_12' in file modules/multiMenu/xoops_version.php line 378
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_13 - assumed '_MI_MULTIMENU_NAME_13' in file modules/multiMenu/xoops_version.php line 392
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_14 - assumed '_MI_MULTIMENU_NAME_14' in file modules/multiMenu/xoops_version.php line 406
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_15 - assumed '_MI_MULTIMENU_NAME_15' in file modules/multiMenu/xoops_version.php line 420
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_16 - assumed '_MI_MULTIMENU_NAME_16' in file modules/multiMenu/xoops_version.php line 434
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_09 - assumed '_MI_MULTIMENU_NAME_09' in file modules/multiMenu/xoops_version.php line 528
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_10 - assumed '_MI_MULTIMENU_NAME_10' in file modules/multiMenu/xoops_version.php line 536
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_11 - assumed '_MI_MULTIMENU_NAME_11' in file modules/multiMenu/xoops_version.php line 544
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_12 - assumed '_MI_MULTIMENU_NAME_12' in file modules/multiMenu/xoops_version.php line 552
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_13 - assumed '_MI_MULTIMENU_NAME_13' in file modules/multiMenu/xoops_version.php line 560
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_14 - assumed '_MI_MULTIMENU_NAME_14' in file modules/multiMenu/xoops_version.php line 568
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_15 - assumed '_MI_MULTIMENU_NAME_15' in file modules/multiMenu/xoops_version.php line 576
Notice [PHP]: Use of undefined constant _MI_MULTIMENU_NAME_16 - assumed '_MI_MULTIMENU_NAME_16' in file modules/multiMenu/xoops_version.php line 584

Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_TITLE_09 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_INDEX_09 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_TITLE_10 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_INDEX_10 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_TITLE_11 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_INDEX_11 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_TITLE_12 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_INDEX_12 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_TITLE_13 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_INDEX_13 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_TITLE_14 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_INDEX_14 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_TITLE_15 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_INDEX_15 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_TITLE_16 in file modules/system/admin/preferences/main.php line 260
Warning [PHP]: constant(): Couldn't find constant _MI_MULTIMENU_MM_INDEX_16 in file modules/system/admin/preferences/main.php line 260

Hi,

I've created a custom block with the content type set to "Auto Format". The block contains text and a url link, which I created with the url formatting button in the XOOPS editor. However, when a user clicks on the url link, XOOPS automatically opens the page in a new window. I checked the html that XOOPS creates, and it inserts target="_blank" into the url (which is why it opens in a new window).

The url is actually pointing to another section of the same site, not to anything outside the site. This is why it is a problem. Is there any way to stop a new window from opening in "Auto Format" mode?

I realize that I have the option of setting the content type to html, and just writing the url link myself (without target="_blank"). However, I like the ease of using the auto format mode for blocks that don't require any complex formatting with html.

Any suggestions for how to keep the page in the same window while using Auto Format mode?

Dave

Hi guardian2k1,

You said:
Quote:

I reread my first post, and it is very confusing the way I asked my first question. I apologize for that.

I'm not worried about any hampering of the site design. I'm primarily wondering how and when XOOPS attempts to make database connections. For example, when a user first loads my home page, if 20 database queries are run during the page load for that user, will the 20 queries count as one user connection? Or, does XOOPS connect and then disconnect for each query that is run? In other words, does 20 queries = 20 connections? I'm assuming that this isn't the case, but I'm not completely sure.

The reason I'm asking this question is because many of the shared hosting plans have a limitation on simultaneous database connections. My plan has a limitation of 15 concurrent connections. Thus, if each query is a connnection (rather than each user generated set of queries equaling one connection), then the connection limitations will be that much more of a problem when managing the limited resources on a shared plan.

I'm using caching, and that reduces the quantity of queries very significantly. I'm very happy with that, since it will boost performance. However, the database connection limitations with shared web hosts is still worrying me. The caching helps a lot, but there is still a significant quantity of queries that are run even with efficient caching.

You said:
Quote:

I agree that it is not an ideal situation to cache a forum, even for 30 seconds. Although, for very busy forums on shared servers, a notice could be posted that new posts will not appear for 30 seconds. That still may be very annoying to users though. And, I'm not really sure what other weird affects may occur with a forum cache. I guess I would have to test and observe, which I may do.

My only reason for considering a forum cache is to prevent reaching the database connection limitations of the shared hosting plans, since forums often generate the most concurrent traffic. If the forum is very busy and on a shared server, then there could be many database connecton errors generated. A 30 second cache may reduce this problem quite a bit. It would be nice if there were even shorter caches available, such as a 10 or 15 second cache, which may go a long way in preventing the limitations from being reached (and not annoying users too much).

Anyway, if I experiment with forum caching, then I will let everyone know how it works out.

Dave

Yes! I would definitely find a forum like that to be very helpful. I think there is especially a need for information on how to get the most out of XOOPS on a shared server, since many people use shared hosting.

The resource availability on shared plans is very limited, which makes efficient XOOPS tuning very critical to performance.

Dave

I was noticing that one of the themes displays the number of queries that are run each time a page is loaded. I was playing around with the cache features, and reduced the home page queries from 52 to around 20. Basically, I'm trying reduce the number of times that the database is accessed and reduce the resources utilized by the CPU. The goal being to minimize resource consumption, to avoid my shared server account from slowing down or locking up during traffic surges.

I have a question about this. With most shared server plans, there is a limit to concurrent MySQL user connections. My particular plan has a 15 user limit, meaning that if 16 users access the database server at the exact same time, then the 16th user will receive an error message. Ok here is my question: When a user accesses my home page, are those 20 queries considered to be occurring under one user connection? Or is there ever a situation where a set of queries (initiated by the same user) are issued through multiple connection requests? I'm hoping that isn't the case, given the limit of 15 concurrent connections.

One other question. Has anyone set a short cache (example: a 30 second cache) to their forum? I'm thinking that maybe a 30 second cache will allow me to run a somewhat busy forum, without the 15 user connection limit being a problem (at low to moderate levels of traffic). My only concern would be the lag in new posts appearing because of the 30 second cache. I'm just trying to figure out a way to squeeze as much as I can out of a shared server, before being forced to upgrade to a VPS, semi-dedicated, or dedicated server.

Dave