131
geekwright
Re: 2.5.8 newbb and xoopspoll - having trouble getting these modules to work together

It looks like there may be a couple of things going on that need some attention. We are looking into them, but in the meantime you can try this.

First, undo any changes you made copying files from xoopspoll module extras directory. You should go back to the versions of those files as distributed with newbb.

Then, in modules/newbb/votepolls.php change line 73 that looks like this:
$optionId = !XoopsRequest::getInt('option_id'0'POST');


and remove the ! sign in front of XoopsRequest, to look like this:
$optionId XoopsRequest::getInt('option_id'0'POST');


This should enable poll votes. There will still be issues with recording votes in multliple option polls, and we will address those in a patch soon.



132
geekwright
Re: 2.5.8 White screen when viewing certain user profiles (newbb - User Profile interaction)

Very interesting issue! I have submitted a patch for this on github.

The attached image code in newbb only worked properly when newbb was the current module (the global $xoopsModule.)

When using the basic system user lookup, there is no current module, and coincidentally, the code causing the fatal error was skipped because the file extensions were not present in a configuration of valid extensions.

When the profile module was used, there was an active module, but the file that defines newbb_attachmentImage() was not loaded because the wrong module directory was being used -- the profile directory, not newbb.

The fix is very simple, in newbb/class/post.php change line 208 from:
include_once $GLOBALS['xoops']->path('modules/' $xoopsModule->getVar('dirname''n') . '/include/functions.image.php');

to:
include_once dirname(__DIR__) . '/include/functions.image.php';


The big mystery was trying to figure out why it ever worked without error ;)

Thanks for the report!



133
geekwright
Re: gBook 1.10 Beta-1 available for testing (XOOPS 2.5.8, PHP 7)

Quote:

safeinsanity wrote:

...
Module: gbook-master
Name: entries


Didn't notice that before. The module directory should be gbook not gbook-master.

That would explain not being able to find a handler.



134
geekwright
Re: Fresh install 2.5.9 beta1

It is good to hear that it is working now. Thanks for letting us know!



135
geekwright
Re: 2.5.8 Upgrade: textsanitizer

I've opened an issue on GitHub to make sure we get that readme.txt updated. Thanks for pointing that out!

In the mean time, changing the two function declarations as follows should clear up any errors that might show up.

...
     
// The code parser
    
public function load($ts
    {

...

    
// Processing the text
    
public static function decode($text$width$height)
    {
...


You don't have to do anything with the extra parameters to decode, they just have to be there to satisfy the inheritance rules set from the parent class.

Quote:

SMEDrieben wrote:
In previous Xoops-version, I made an additonal TextSanitizer extension according to the readme.txt:

...

It now generates an message:

OnbekendDeclaration of MytsRef::decode() should be compatible with MyTextSanitizerExtension::decode($url$width$heightin bestand /class/textsanitizer/ref/ref.php regel 28


How can I solve this message ?

SMEDrieben



136
geekwright
Re: 2.5.8 :: Update Error : ParseError: syntax error, unexpected

There is a tool, php7cc, that we've used a lot when adapting code to PHP7. You might find it helpful.

It is available here:https://github.com/sstalle/php7cc



137
geekwright
Re: 2.5.8 :: Update Error : ParseError: syntax error, unexpected

Quote:

wishcraft wrote:
When i got it up and running I got the following error: Error : ParseError: syntax error, unexpected 'new' (T_NEW)


The most likely cause is a line like this:
$variable =& new SomeObject();


The problem is the & by reference operator.

Objects are always references now, and PHP7 complains if you use the by reference assignments with them. But when you add new in one of those assignments, it becomes a parse error -- it can't use it in that context.

Finding and fixing any occurrences like that example should fix it.



138
geekwright
Re: MyAlbum 3.07 pre-RC3 available for testing

Small change to line 88 fix (no leading "$"):
parent::__construct($title'groupperm_form''''post');



139
geekwright
Re: Fresh install 2.5.9 beta1

Quote:

for example "Warning: include_once(../class/module.textsanitizer.php): failed to open stream: No such file or directory in F:\wamp\www\xoops259\install\include\common.inc.php"


What does the directory structure of your web root look like? That error suggests it has been corrupted somehow.

At a minimum, you should have these directories in the root:
class
Frameworks
images
include
install
kernel
language
modules
themes
uploads

There might be more, but these should always be there.

If you have not intentionally relocated the xoops_data and xoops_lib, they would also be in the root.

For a fresh install, you should not have a mainfile.php in the root. There is an exception if you are using the one from extras directory due to permission issues.

Relative directories are used in the installer, and the full paths are established as it runs. There is no legitimate way it should not be able to find things in ../class if the structure from the htdocs directory in the repository is maintained in the web root.



140
geekwright
Re: Antispam solutions

Quote:

option wrote:
and Recaptcha for xoops ....
https://github.com/bitcero/reCaptcha
:O


There is a certain elegance in a "let Google fight the war for you" strategy




TopTop
« 1 ... 11 12 13 (14) 15 16 17 ... 22 »



Login

Who's Online

108 user(s) are online (75 user(s) are browsing Support Forums)


Members: 0


Guests: 108


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits