xoops forums

Forum Index


Board index » All Posts (geekwright)




geekwright

Quite a regular
Posted on: 1/20 2:43
geekwright
geekwright (Show more)
Quite a regular
Posts: 231
Since: 2010/10/15
#1

Re: Xoops Database Class

Unfortunately, I am not aware of any stand alone documentation of the XoopsDatabase classes.

Good news, the classes do have some useful internal documentation:
http://api.xoops.org/2.5.9/class-XoopsMySQLDatabase.html

In general, the methods correlate closely to the mysqli functions of PHP, so the documentation there is useful: http://php.net/manual/en/book.mysqli.php


geekwright

Quite a regular
Posted on: 1/13 21:55
geekwright
geekwright (Show more)
Quite a regular
Posts: 231
Since: 2010/10/15
#2

Re: protector.php not found

Sorry to hear you had so many issues. We did test against 2.3 but since 2.3 won't install on anything that can run 2.5.9, just getting the core running so it could be upgraded was not simple. It would have been nice to have a VM with a real working 2.3 system to test against, but we didn't have that.

From what you described, the manual mainfile.php changes needed in 2.3 to enable protector, caused some new protector code to be loaded before the autoloader for Xmf was started. I'll add a note to the manual to remove that code before starting the upgrade.

Quote:

Moonrakre wrote:
... because the upgrade instructions didn't says to copy xoops_data folder to the installed _data folder (similar to _lib).

Ooops! Thanks for pointing that out. I'll put in a correction for that, too.

Just for reference, the xoops_data instructions are only missing from the quick overview. It does mention that in the detailed instructions:

Copy New Files to the Site
... You should copy the xoops_data and xoops_lib directories to wherever these were relocated during the install. ...

Glad you got it up and running, and thanks for the reports.


geekwright

Quite a regular
Posted on: 12/27 17:24
geekwright
geekwright (Show more)
Quite a regular
Posts: 231
Since: 2010/10/15
#3

Re: total number of search result in search php

There is no point in the XOOPS search process where a total number of results is calculated. The individual module search functions respond to a limit (maximum number of results to return) and offset (skip over this many results before a set of at most 'limit' results.) No totals are generated.

I would assume this design was intended to limit the potential database load for each search transaction.


geekwright

Quite a regular
Posted on: 12/27 14:28
geekwright
geekwright (Show more)
Quite a regular
Posts: 231
Since: 2010/10/15
#4

Re: Error during the installation initial setting

Try changing the MySQL host to "127.0.0.1" instead of "localhost".

By default the installer will use "localhost" as the MySQL host. In some stacks on some versions of Windows that will cause issues. The underlying issue is each connection experiencing a time out waiting on a response from MySQL due to IPV6 vs. IPV4 versions of localhost.

There is a longer discussion of this here: https://xoops.org/modules/news/article.php?storyid=6758


geekwright

Quite a regular
Posted on: 12/10 2:12
geekwright
geekwright (Show more)
Quite a regular
Posts: 231
Since: 2010/10/15
#5

Re: xoops 2.5.9 installation with non-english language

Quote:

aerograf wrote:
If you install xoops by default, with English, some variables are written to the database, which you can then change only through the mysql editor.
For example table profile_field


There is no provision in the profile module to localize the strings in profile_field. You can create totally new fields, so it is possible no language constant ever existed. Only the initial setup uses the constants, after that whatever is entered in the profile module admin area is used.

If another language is properly installed as the default when the profile module is installed, it should use that language as the starting values in profile_field. To dynamically translate the profile_field field_title, you would need to use a multi-language hack like xlanguage.

Also, I think Michael is correct that the admin page screenshot issues are strings in the new transition theme:
modules/system/themes/transition/language/english/admin.php

Add translations for that file, and it should fix that issues.


geekwright

Quite a regular
Posted on: 2017/10/13 16:21
geekwright
geekwright (Show more)
Quite a regular
Posts: 231
Since: 2010/10/15
#6

Re: New 2.5.9 install path problem

Quote:

Dante7237 wrote:
...
So you're telling me that the installer will prompt me for input rather than expecting paths to be present in mainfile?


Right! There is no mainfile.php before the installer runs. Enter the correct paths when prompted, and it will verify them. After that, the installer will create the new mainfile.php once all the needed information has been gathered.

Here is the relevant documentation on GitBook.


geekwright

Quite a regular
Posted on: 2017/7/26 18:29
geekwright
geekwright (Show more)
Quite a regular
Posts: 231
Since: 2010/10/15
#7

Re: Error when trying to edit an article on publisher

Looks like we got a little detail out of sequence.

The Xmf\Request::hasVar() method was added to XMF after XOOPS 2.5.8 was released. The current Publisher version was developed along with XOOPS 2.5.9, which does include that method. I'm not totally sure, but it looks like it was my mistake. Sorry!

There are a couple of ways you could fix it today.

If you are comfortable using composer, running the following command in the class/libraries directory would update XMF to the current version:
composer update


Alternatively, you could update just the Request class file, by copying this file:
https://raw.githubusercontent.com/XOOP ... .2.10/src/Xmf/Request.php

over this file in your XOOPS installation:
class/libraries/vendor/xoops/xmf/src/Xmf/Request.php

Either one of those should get you through the error you are encountering.


geekwright

Quite a regular
Posted on: 2017/7/26 1:07
geekwright
geekwright (Show more)
Quite a regular
Posts: 231
Since: 2010/10/15
#8

Re: Protector and Bad Ips

Actually, that looks like it is working.

Protector's bad IP works at the application level. That means Apache still gets the request, and launches the task. Protector checks the list, and when it matches, it sends out a short message like "You are registered as BAD_IP by Protector." Then it ends the task.

In the apache log, that will still be a 200 (found) with a small byte count.

In your log screen shot, all the 216.244.66.230 requests are logged as:
...HTTP/1.0" 200 289 "-"...

The 289 is the byte count of the reply, which is about right for the banned message, and much too small for a real page view.

That indicates that it is doing what it is supposed to do. To stop the transactions completely would require a firewall that stopped the requests before they reached Apache. The protector filter is just minimizing the load as best it can from inside the PHP script.


geekwright

Quite a regular
Posted on: 2017/7/25 16:15
geekwright
geekwright (Show more)
Quite a regular
Posts: 231
Since: 2010/10/15
#9

Re: Protector and Bad Ips

Ending with a dot should ban everything that matches up to the dot, i.e. 216.244.66. will ban 216.244.66.1, 216.244.66.2, 216.244.66.3, etc.

I've tested that on 2.5.7 and 2.5.9, and both are working as expected here. (The code changed to support IPV6 between the two versions.)

If there was a problem reading or writing the xoops_lib/modules/protector/config/badips file, you would be able to see that in the protector center.

I'm not sure what is going on in your case, as it works here.


geekwright

Quite a regular
Posted on: 2017/7/23 15:58
geekwright
geekwright (Show more)
Quite a regular
Posts: 231
Since: 2010/10/15
#10

Re: Protector and Bad Ips

The wildcard is supposed to be ending the address with a dot, i.e. 216.244.66.

What XOOPS version are you using?



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