6503
There are some links here
One of them (click here) says:
Quote:
In your case you could have a database crash. If this is the case, you might need to repair your tables via phpMyAdmin.
One of them (click here) says:
Quote:
"Got error 134 from storage engine"
-- you can ignore the error. It usually means that the script is trying to remove a non-existing record from database, which makes no harm if the removal is not executed; or it could indicate crash of your database, which obvious not your case.
In your case you could have a database crash. If this is the case, you might need to repair your tables via phpMyAdmin.
6504
Correct! 2.0.18.2 is the latest and officially supported version of XOOPS.
The 2.2 branch was something that didn't work out, and you can read more about it here...
The 2.3 version will merge those two version into one version going forward. This will help us to deploy our limited resources in a more efficient way.
The 2.2 branch was something that didn't work out, and you can read more about it here...
The 2.3 version will merge those two version into one version going forward. This will help us to deploy our limited resources in a more efficient way.
6505
The main thing is that this is a "D3" module, i.e. it uses "XOOPS_TRUST_PATH". For more info about it see here
To install these modules, you have to have defined first the "XOOPS_TRUST_PATH".
Then copy content of the /webphoto/xoops_trust_path over there
Then copy content of the /webphoto/html/modules to your main /modules subdirectory.
Then go to Admin, and install that module
To install these modules, you have to have defined first the "XOOPS_TRUST_PATH".
Then copy content of the /webphoto/xoops_trust_path over there
Then copy content of the /webphoto/html/modules to your main /modules subdirectory.
Then go to Admin, and install that module
6506
It's because different modules are developed by different developers, and they approached the issue from a different angle.
But I agree with you that it would beneficial to have the same behaviors, and I hope, we'll be able to standardize it across modules in the future, as we get closer to XOOPS 3.0.
But I agree with you that it would beneficial to have the same behaviors, and I hope, we'll be able to standardize it across modules in the future, as we get closer to XOOPS 3.0.
6510
For the left menu, go to
/modules/system/templates/blocks/system_block_mainmenu.html
and insert after line 12 (which is: "<!-- end module menu loop -->")
That should do it.
I am not sure what script do you use for the top, but just follow the way it was done for the entries on top.
/modules/system/templates/blocks/system_block_mainmenu.html
and insert after line 12 (which is: "<!-- end module menu loop -->")
<a class="menuMain" href="http://supportforums.hostedwith.us/forum/">Forums</a>
That should do it.
I am not sure what script do you use for the top, but just follow the way it was done for the entries on top.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|