xoops forums

Forum Index


Board index » All Posts (geekwright)




geekwright

Quite a regular
Posted on: 2/15 19:52
geekwright
geekwright (Show more)
Quite a regular
Posts: 255
Since: 2010/10/15
#1

Re: Xoops 2.5.8.1 Installing issue

Quote:

Userino wrote:
...
Apache has permission over the Xoops Folder.


Only partially. With SELinux, you'll need to change the context for the web directories, too. Here is an article with some details:

https://www.svnlabs.com/blogs/centos-7 ... p-writeaccess-permission/


geekwright

Quite a regular
Posted on: 2/15 2:50
geekwright
geekwright (Show more)
Quite a regular
Posts: 255
Since: 2010/10/15
#2

Re: Xoops 2.5.8.1 Installing issue

Most likely, the user (or group) the webserver's PHP processes run under can't create a file in and/or write to the the xoops_data directory.

IIRC, in CentOS it is the "apache" user that needs to have the permissions. Under debian based distros it is the www-data user.


geekwright

Quite a regular
Posted on: 12/16 17:54
geekwright
geekwright (Show more)
Quite a regular
Posts: 255
Since: 2010/10/15
#3

Re: Database: How do I set a column value to NULL

Quote:
luciorota wrote:
...
I think it is a Xoops limit...

Sadly, you are correct.

I did a dive into the code when I saw your question, and the XoopsObject family seems to have no direct support for NULLs. Updating a column to NULL presently would require building the update query manually and running it with the database query() method.

Likewise the handling of a NULL value in selects seems to be datatype dependent, more like a side effect.


geekwright

Quite a regular
Posted on: 12/16 17:26
geekwright
geekwright (Show more)
Quite a regular
Posts: 255
Since: 2010/10/15
#4

Re: xoops Password rules and password expiry

XOOPS could really use some modern password policy management tools.

My first impulse was to suggest expanding the profile module, but on closer inspection, using existing events and adding a few new ones would allow us to support a module(s) dedicated just to enhanced password policy. Unfortunately, that solution isn't available to deploy today

I will make sure that we have all the events needed to support such a module in place very soon.

Meanwhile, the fastest "hack" I can think of would be to tap into an existing Active Directory, using it as the authentication option for your XOOPS system. I don't know it that would be possible or practical for your environment.

As to resetting all passwords, you could update the "pass" column on the users table with some garbage string for all the users you want to reset. Each user would then have to go through the lost password mechanism to set a new password.


geekwright

Quite a regular
Posted on: 12/4 17:38
geekwright
geekwright (Show more)
Quite a regular
Posts: 255
Since: 2010/10/15
#5

Re: FOREIGN KEY

Since the SqlUtility class doesn't recognize the table name in the REFERENCES clause, you will have to add the constraint outside of the module's mysql.sql file.

I would suggest generating and running the SQL to perform an "ALTER TABLE ... ADD FOREIGN KEY ..." inside the onInstall file's xoops_module_install_dirname() function.

Longer term, this should become a non-issue as we progress toward schema definitions rather than SQL for table creation.


geekwright

Quite a regular
Posted on: 2018/11/12 2:18
geekwright
geekwright (Show more)
Quite a regular
Posts: 255
Since: 2010/10/15
#6

Re: Error in animal pedigree software Error : Handler does not exist

I suspect the clue is in the module name, "pedigree-master".

That is the name GitHub assigns to the download, and unfortunately it is wrong. The directory name for the module should be just "pedigree".

- Uninstall the module pedigree-master
- Rename the directory from pedigree-master to pedigree
- Install the module pedigree

That should solve the issue. Mamba is the expert on pedigree, and I'm sure he will chime if there are any further issues..


geekwright

Quite a regular
Posted on: 2018/11/11 20:45
geekwright
geekwright (Show more)
Quite a regular
Posts: 255
Since: 2010/10/15
#7

Re: Internal Error - Upgrade from 2.3.3b to 2.5.8

Quote:

stonez wrote:
...
2. PiCal module: Error: Call to undefined function ereg()
...


The whole family of ereg functions were removed in PHP 7. They had been deprecated since PHP 5.3.

Here is a stackoverflow explanation and recipe for replacing ereg():
https://stackoverflow.com/questions/62 ... xpressions-to-preg-in-php


geekwright

Quite a regular
Posted on: 2018/11/10 19:55
geekwright
geekwright (Show more)
Quite a regular
Posts: 255
Since: 2010/10/15
#8

Re: Internal Error - Upgrade from 2.3.3b to 2.5.8

The most likely cause of the error is some code in an old module which includes the phrase:
=& new

An example of this would look something similar to:
$object =& new ClassName();


That syntax was deprecated in PHP 5, but is now an error in PHP 7. The "=&' is assigning a value by reference, but the return of "new" is already a reference. Remove the "&" and that should fix it.

It would be worth checking to see if any PHP 7 ready upgrades are available for any modules you may be using.


geekwright

Quite a regular
Posted on: 2018/10/17 15:21
geekwright
geekwright (Show more)
Quite a regular
Posts: 255
Since: 2010/10/15
#9

Re: How to install a xoop back up on xampp local host

Install your stack (i.e. XAMPP or WAMP) and make sure it is working first.

Here is a section of the installation manual dealing with moving a site:
https://github.com/XoopsDocs/xoops-2.5 ... ree/master/en/book/moving

You can follow those instruction to adapt your backup files to the local environment.


geekwright

Quite a regular
Posted on: 2018/10/16 22:29
geekwright
geekwright (Show more)
Quite a regular
Posts: 255
Since: 2010/10/15
#10

Re: Smarty 3.1.33

There are some potential issues. These are the main ones:

1) Since we expose Smarty directly, the BC layer for v2 would be required. It is good, but not 100% perfect. Alone, this would probably not be a blocker, but it could break previously working code.

2) Due to changes in parsing, things as simple as extra spaces or missing quotes may cause unintended results or errors in some circumstances. These were harmless in v2.

3) Many XOOPS templates have historically relied on an unassigned variable to evaluate as false. While this may still work, it will produce error messages, sometimes in log file filling quantities..

The code and templates included in XOOPS and the more actively maintained modules have some of these possible errors corrected already. There are, however more modules, and even more templates and themes that may never have been checked. Those are the ones that may break sites which have worked for years on upgrading.

With the 2.5 series, we want to encourage upgrades especially for security reasons. Adding features we suspect may cause issues is something we want to avoid if at all possible. The next generation XOOPS will include the latest Smarty, and as a major upgrade, the BC issues will be expected, acceptable and documented.



TopTop
(1) 2 3 4 ... 17 »