71
Ne_rpa
Support for Jadoogaran.org
  • 3/9 23:46

  • Ne_rpa

  • Just popping in

  • Posts: 6

  • Since: 3/9 23:12


Hi everyone,
And hi mamba!

I hope everyone is well.
jadoogaran.org website has been using the xoopssystem since 2004. But it hasn't been updated for a long time and the latest version of xoops is 2.5.6. i'am new Technical Manager of site and i'm working for new upgrade. i translated the last xoops (2.5.11) to persian. i'm testing it and it's really become better. right now we are creating new theme and working on modules. so much of our old modules has no more updates anymore and we dont know what we should do. modules like article, xcgallery, wfdownlaods and xhelp. but my main problem is Xoopspoll modules. both final and beta version is not working with newbb 5.1.0. i also test it with newbb 5.0.0 but has same problems.

also i need some modules for daily private diary and private notebook but i didnt find anything. im also right now working on translating modules and testing them.

and i need an Alternative modules for xhelp in new xoops.

please help me and tell me what i should do with my modules issue.
and i want to release my persian version of xoops and modules. where can i do this?

thank for your help.



72
Eunydd
Re: Theme Administration User Interface
  • 2/24 10:57

  • Eunydd

  • Just popping in

  • Posts: 8

  • Since: 2022/10/8


What else ? Probably everything else which isn't in a Block (Login, User Menu, Main Menu etc.) - without understanding how feasible this is ! Some things are already configurable as you point out, and pulled by the theme, Sitename, Banners also - but part of the problem, as a new user, is that you aren't aware of this or understand the system conventions. So it's sort of 'all or nothing'.

Perhaps the difficulty with this is that it would need to be Theme specific, so an admin UI would be on a per theme basis - although not obligatory and perhaps only done for one. Initially I'd probably just do an admin panel for Xswatch4 and make this the default theme. So a new Xoops user would see this first and could be directed to the Theme Admin UI, immediately change the theme interactively, and be up and running within a few minutes.



73
Mamba
Re: Theme Administration User Interface

The site name you can set already in the Admin Preferences:
yoursite.com/modules/system/admin.php?fct=preferences&op=show&confcat_id=1

so we wouldn't have to change it, since the them is pulling it from there, and when you change the theme, you don't have to change the site name.

But I agree for with the logo and color scheme! What else?

If somebody could make these changes and submit to GitHub, it would be a nice improvement!
Support XOOPS => DONATE
Use 2.5.11 | Docs | Modules | Bugs



74
Eunydd
Theme Administration User Interface
  • 2/20 11:06

  • Eunydd

  • Just popping in

  • Posts: 8

  • Since: 2022/10/8


Theme Administration UI

I float this as an idea having found the need to hack template code even to make simple changes very frustrating - which possibly puts off new xoops users altogether. One of the first things you do is pick a Theme for your site (xSwatch4 in my case). These are invariably Responsive 3 panel, 2 header, 2 footer designs because this meets most needs - you only need one or two. A Theme Administration UI, enabling editing of site name, logo, colour scheme etc. would get people up and running very quickly and encourage further use methinks.



75
Mamba
Re: Choice of editors for the Newbb module

Please keep us posting!
Support XOOPS => DONATE
Use 2.5.11 | Docs | Modules | Bugs



76
Mamba
Re: Protector Module - Error : TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool

Great to hear that you've fixed that!

Thanks for letting us know!
Support XOOPS => DONATE
Use 2.5.11 | Docs | Modules | Bugs



77
Eunydd
Re: Protector Module - Error : TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool
  • 2/9 16:53

  • Eunydd

  • Just popping in

  • Posts: 8

  • Since: 2022/10/8


Thanks, this hinted at a Permissions problem and once I had mastered PHP Error Logging the fix was straightforward.

The PHP Error :
Warning: fopen(/var/local/lib/xoops/data/protector/configcachea07794): Failed to open stream: Permission denied in file /var/local/lib/xoops/lib/modules/protector/class/protector.php line 184
Error: TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given in file /var/local/lib/xoops/lib/modules/protector/class/protector.php line 185

Fix:
Change directory/file Ownership to root:www-data and Permissions to 0775/0664



78
Skype-Fr
Re: Choice of editors for the Newbb module
  • 2/9 16:00

  • Skype-Fr

  • Just popping in

  • Posts: 37

  • Since: 2006/4/27


Hi Mamba,

This code causes the HTTP : ERROR 500 !

I'll keep looking on my side ...

G.



79
Mamba
Re: Protector Module - Error : TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool

I installed XOOPS 2.5.11 on PHP 8.2.27 and also on PHP 8.4, and couldn't replicate the error.

This error happens normally when you want to open a file using
fopen()
do something, and then want to write the results to the file using
fwrite()


When the file couldn't be open in the first place, then fopen() will be false, and you will get your error when you try to write to that file

So you would need to place a check for false before you fwrite()

In code like this:

$fp = @fopen($protector->get_filepath4group1ips(), 'w');
        if (
$fp) {
            @
flock($fpLOCK_EX);
            
fwrite($fpserialize(array_unique($group1_ips)) . "n");
            @
flock($fpLOCK_UN);
            
fclose($fp);
        } else {
            
$error_msg .= _AM_MSG_GROUP1IPSCANTOPEN;
        }


you could check for false:

$fp = @fopen($protector->get_filepath4group1ips(), 'w');
if (
false !== $fp) {


or you could check for false and use Exception:

$fp = @fopen($protector->get_filepath4group1ips(), 'w');
if (
$fp === false) {
    throw new 
FileOpenException("Failed to open file for writing: $filePath (mode: 'w')");
}


Try one by one for the all the fwrite() cases within /xoops_lib/modules/publisher, and see if that helps to identify the issue.

Let us know if that helped to identify the issue.

Also, if I remember correctly, somebody said that there were some problems with an installation provided by the ISP, so you might download the full XOOPS 2.5.11 and reinstall it.

If this is a testing site, you might also download the Beta of XOOPS 2.5.12 and see if the problem is still there.
Support XOOPS => DONATE
Use 2.5.11 | Docs | Modules | Bugs



80
Eunydd
Protector Module - Error : TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool
  • 2/8 20:21

  • Eunydd

  • Just popping in

  • Posts: 8

  • Since: 2022/10/8


I have a clean install of Turnkey Linux XOOPS 18.0 appliance running in VirtualBox 7.1.6 (no Guest Additions). This installs without error and initially XOOPS runs without error : the only modules present are System, Private Messaging, User Profile and Protector. However when I amend Protector Preferences there is a fatal error (even when nothing is actually amended but Go is pressed) :

Error : TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given

The same is true after applying Updates to all four modules, which are error-free in themselves.

My debugging skills have reached there limit and I could do with some support. Any ideas?
Thanks.

XOOPS 2.5.11 Stable
Protector 3.6.2_Stable
PHP 8.2.26
MySql 10.11.6-MariaDB-0+deb12u1
Apache 2.4.6.2




TopTop
« 1 ... 5 6 7 (8) 9 10 11 ... 29443 »



Login

Who's Online

141 user(s) are online (87 user(s) are browsing Support Forums)


Members: 0


Guests: 141


more...

Donat-O-Meter

Stats
Goal: AU$15.00
Due Date: Jul 31
Gross Amount: AU$0.00
Net Balance: AU$0.00
Left to go: AU$15.00
Make donations with PayPal!

Latest GitHub Commits