6033
There are different themes that you could adjust to you needs, like for example:
Delphic
Enzyme
Or you can use a HTML template and adjust it to XOOPS by following this tutorial (in Spanish)
Delphic
Enzyme
Or you can use a HTML template and adjust it to XOOPS by following this tutorial (in Spanish)
6034
Quote:
It can't, as XOOPS 2.5.6 was released in April 2013
As Zyspec said earlier, you should upgrade to PHP 5.3.7+, with PHP 5.4 recommended! Most good hosts offer just to change one setting in the config, and you're running the upgraded PHP in 3 minutes!
Please read:
5 Reasons to Consider Upgrading Your PHP Platform
The author, Lorna Mitchell, offers her list of five things, each with a bit of summary and a few links to more information on the topics:
- Improved Performance
- Security and Support
- New Syntax
- Traits
- Built In Webserver
Also, XOOPS won't act strange "out of the blue" - there had to be a change to cause it. Check the logs fort the host changes, and go back and see if you have changed something but forgot about it ...
This site is running with no update from 3-4 years ago.
It can't, as XOOPS 2.5.6 was released in April 2013
As Zyspec said earlier, you should upgrade to PHP 5.3.7+, with PHP 5.4 recommended! Most good hosts offer just to change one setting in the config, and you're running the upgraded PHP in 3 minutes!
Please read:
5 Reasons to Consider Upgrading Your PHP Platform
The author, Lorna Mitchell, offers her list of five things, each with a bit of summary and a few links to more information on the topics:
- Improved Performance
- Security and Support
- New Syntax
- Traits
- Built In Webserver
Also, XOOPS won't act strange "out of the blue" - there had to be a change to cause it. Check the logs fort the host changes, and go back and see if you have changed something but forgot about it ...
6035
Thanks 
The problem of the default theme is resolved by changing the arrangement of folders css, js, img, icons in assets
In fact, for this I changed the file class/theme.php paths by adding the prefix assets before
For the rest, I'm working for both the left menu for other problems to solve.
As you know I am committed each time the files in SVN
P.S: Don't worry if I don't commit immediately to GitHub, only time to finish well.
The problem of the default theme is resolved by changing the arrangement of folders css, js, img, icons in assets
In fact, for this I changed the file class/theme.php paths by adding the prefix assets before
For the rest, I'm working for both the left menu for other problems to solve.
As you know I am committed each time the files in SVN
P.S: Don't worry if I don't commit immediately to GitHub, only time to finish well.
6036
This site is running with no update from 3-4 years ago.
My hoster says that no php upgrade/change has been done in this time.
The problem used to happen from time to time previously, but now it happens every time.
My hoster says that no php upgrade/change has been done in this time.
The problem used to happen from time to time previously, but now it happens every time.
6037
Many times, we request the users asking for support, to provide us with the info about their XOOPS installation.
To make it easier, this hack, based on suggestion from Jim Garrett (aka Zyspec), adds a link in the Admin:
When you click it, it will extract the info about your configuration (see an example below), and place it in your clipboard. You just need to paste it in the XOOPS Forums, when you ask for help.
This is right now a proof of concept, looking for testers. Please don't use it on your production sites!
This is only for XOOPS 2.5.7.1 and 2.5.8 beta
EXAMPLE: this would be copied to your clipboard:
Quote:
To make it easier, this hack, based on suggestion from Jim Garrett (aka Zyspec), adds a link in the Admin:
When you click it, it will extract the info about your configuration (see an example below), and place it in your clipboard. You just need to paste it in the XOOPS Forums, when you ask for help.
This is right now a proof of concept, looking for testers. Please don't use it on your production sites!
This is only for XOOPS 2.5.7.1 and 2.5.8 beta
EXAMPLE: this would be copied to your clipboard:
Quote:
XOOPS 2.5.8_Beta1
PHP Version: 5.6.5
mySQL Version: 5.6.22
Server API: apache2handler
OS: WINNT
safe_mode: Off
register_globals: Off
register_globals: Off
allow_url_fopen: On
fsockopen: On
allow_call_time_pass_reference: Off
post_max_size: 8M
max_input_time: 120
output_buffering: 4096
max_execution_time: 60
memory_limit: 512M
file_uploads: On
upload_max_filesize: 2M
Active Modules:
---------------
eXtCal 2.38
News 1.71
Publisher 1.02
System 2.11
User Profile 1.86
Wfdownloads 3.23
Deactivated Modules:
---------------
Forum 4.33
My Links 3.11
Private Messaging 1.1
Protector 3.52
6038
Timgno, nice work, congratulations! :)
Few comments, after spending only limited time looking at this:
- make sure that this theme doesn't impact existing Admin themes. For example, when I went bock to the default, the "look and feel" was changed, even if I cleared the cache
- if you can, please leave or re-implement the top drop-down menus, so the users who prefer that way are not forced to use the side menus
- please make sure that when I click on the menu selection, it doesn't close automatically. For example, when I go to Dropdown Menu -> Modules -> System and click on "Avatars", the menu closes, i.e. I cannot check anymore the "Banners", unless I repeat the whole process again. The other way is to make the Breadcrumb work, so when I am in "Avatars", I can click on "System" link in the Breadcrumb, and then it will open the "System" in the side "Dropdown Menu".
Of course, this is probably still Alpha, so many features are still missing, but as you progress and improve it, please keep it in mind.
Congratulations again...
Few comments, after spending only limited time looking at this:
- make sure that this theme doesn't impact existing Admin themes. For example, when I went bock to the default, the "look and feel" was changed, even if I cleared the cache
- if you can, please leave or re-implement the top drop-down menus, so the users who prefer that way are not forced to use the side menus
- please make sure that when I click on the menu selection, it doesn't close automatically. For example, when I go to Dropdown Menu -> Modules -> System and click on "Avatars", the menu closes, i.e. I cannot check anymore the "Banners", unless I repeat the whole process again. The other way is to make the Breadcrumb work, so when I am in "Avatars", I can click on "System" link in the Breadcrumb, and then it will open the "System" in the side "Dropdown Menu".
Of course, this is probably still Alpha, so many features are still missing, but as you progress and improve it, please keep it in mind.
Congratulations again...
6039
Don't have any specifics to help other than XOOPS 2.5.6 says it requires:
Quote:
Quote:
PHP:
Any PHP version >= 5.3.7 (PHP 5.4+ is strongly recommended)
6040
One of my sites has an strange behaviour that makes impossible to login if you don't delete cookies before, or if wait for a long long time (may be 1 day, not sure).
My site is configured like this:
- URL is a subfolder of main domain: https://www.????mydomain.com/courses/
- PHP Version 5.2.17
- Xoops: 2.5.6.
- Protocol: https
- Name for user cookies: x??????_user
- Use custom session: yes
- Session name: x?????_session
- Session expiration: 60
This error happens in this way:
- Fist login try of the day: everything goes ok, I can use the site normally.
- After use, I don't close session manually, simply leave the site loaded in the browser.
- After 1 hour or more, if I try to navigate again through the site I get the usual permissions error (needed to be logged to use the site).
- I try to log and the site shows that I have logged correctly with the redirect page (It doesn't use jGrowl redirect)
- After been redirected the main page is shown, but always logging block is displayed as sessions is actually closed.
- If I directly load site home page, It shows the login block.
If I delete cookies (only the ones of my site) I can log again without troubles.
Please help.
My site is configured like this:
- URL is a subfolder of main domain: https://www.????mydomain.com/courses/
https://www.????mydomain.com
is a different site with different files, database, cookie and session names, etc.) - PHP Version 5.2.17
- Xoops: 2.5.6.
- Protocol: https
- Name for user cookies: x??????_user
- Use custom session: yes
- Session name: x?????_session
- Session expiration: 60
This error happens in this way:
- Fist login try of the day: everything goes ok, I can use the site normally.
- After use, I don't close session manually, simply leave the site loaded in the browser.
- After 1 hour or more, if I try to navigate again through the site I get the usual permissions error (needed to be logged to use the site).
- I try to log and the site shows that I have logged correctly with the redirect page (It doesn't use jGrowl redirect)
- After been redirected the main page is shown, but always logging block is displayed as sessions is actually closed.
- If I directly load site home page, It shows the login block.
If I delete cookies (only the ones of my site) I can log again without troubles.
Please help.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|