1
slider84
Bug in Xoopspoll 1.40 beta2
  • 2015/7/20 8:41

  • slider84

  • Just popping in

  • Posts: 21

  • Since: 2013/8/16


Hi,

In file /modules/xoopspoll/templates/xoopspoll_results.tpl :

<{include file="db:xoopspoll_results_renderer.html"}>

must be replace by:
<{include file="db:xoopspoll_results_renderer.tpl"}>



2
slider84
Re: XOOPS MyMenus 1.51 RC-1 released for testing
  • 2015/3/1 5:40

  • slider84

  • Just popping in

  • Posts: 21

  • Since: 2013/8/16


It's the rc2 I tested



3
slider84
Re: XOOPS MyMenus 1.51 RC-1 released for testing
  • 2015/2/28 18:28

  • slider84

  • Just popping in

  • Posts: 21

  • Since: 2013/8/16


Work fine for me. No bugs found

Xoops 2.5.7.1 - Debian 7.8 - Apache 2.2.22 - MySQL 5.5.41 - Php 5.4.36



4
slider84
Re: XOOPS 2.5.7 Final Release Issues
  • 2014/10/3 15:24

  • slider84

  • Just popping in

  • Posts: 21

  • Since: 2013/8/16


Hi all,

Someone else have the same problem with Profile rights ?



5
slider84
Re: XOOPS 2.5.7 Final Release Issues
  • 2014/9/28 9:49

  • slider84

  • Just popping in

  • Posts: 21

  • Since: 2013/8/16


I think there is a bug in the rights of the Profile module in 2.5.7:
The field access rights are reversed from the checkbox status.

To reproduce the bug:
1- In the permissions tab profile select from the dropdown list: "Can be searched on the part of these groups"
2- Remove all the rights of all groups (yes ...)
3- Search a user from pseudo.
Well, well, the admin can still find user... at this limit this doesn't traumatize me but other groups can also !

4 In contrast, if now we check all the group for admins, admins can no longer find anything !

It looks like a reversal of the value of the checkboxes and real state of rights.
Or the text of the dropdown list would be: Can not be searched on the part of these groups. Not very logical...

Tested on a brand new 2.5.7 an on upgrade from 2.5.6.
I tested only this option,i had no time for other options (Editable field from profile, profiles can be viewed by these groups...)



6
slider84
Re: Publisher 1.02 Beta 3 for XOOPS 2.5.7 ready for testing
  • 2014/6/23 8:38

  • slider84

  • Just popping in

  • Posts: 21

  • Since: 2013/8/16


Hi,

On update:
Old template files (.html) are not deleted.
Old directories (images, js, css) not deleted too.



7
slider84
Re: XOOPS 2.5.7 Final Release Issues
  • 2014/6/20 16:28

  • slider84

  • Just popping in

  • Posts: 21

  • Since: 2013/8/16


Thank you very much geekwright for your detailed response.



8
slider84
Re: XOOPS 2.5.7 Final Release Issues
  • 2014/6/20 7:57

  • slider84

  • Just popping in

  • Posts: 21

  • Since: 2013/8/16


I have a small problem with the following link in protector (tab 'security advisory')

That check PHP files inside TRUST_PATH are set to read-only (it must be 404.403 or 500 error)

The link points to:
http://myserver/www/xoops_lib/modules/protector/public_check.php
(or http://localhost/www/xoops_lib/modules/protector/public_check.php for local installation)

but have to point to:
http://myserveur/xoops_lib/modules/protector/public_check.php
There are additionnal www.

My analysis after several tests and fresh install:
This occurs only if 2.5.7 is installed (not tested with 2.5.6) on a debian based server
(I do not have any other Linux distributions to test) in local or intranet.
In my case, tested on two different machines:
- Ubuntu 12.04 LTS server with PHP 5.3.10 and Apache 2.2.22.
- Debian 7 with PHP 5.4.4 and Apache 2.2.22.
- Default LAMP installation under / var / www (Hey, it looks like the three additionnal w)

So far nothing special and a website works perfectly here.

If I install a 2.5.7 at this point, I have the problem of protector link which does not work with the additionnal www.
But if I create a subdirectory (with the well alias) eg / var/www/site1 and I install 2.5.7 here the protector link is good.
I'd like to know if anyone else has the same problem on a LAMP configuration or if someone could test to confirm whether or not the problem is in protector or the configuration of my machines?



9
slider84
Re: XOOPS 2.5.7 Final Release Issues
  • 2014/6/19 17:52

  • slider84

  • Just popping in

  • Posts: 21

  • Since: 2013/8/16


Hi Mamba,

Quote:
Did you updated the System module? Did you clear the Cache?

No updates for me: Brand new Xoops 2.5.7 (with protector and default theme)+ fresh install of Publisher.
Quote:
publisher tabs when submit article not working - no tabs
Tabs ok in submit form

No tabs in administration section (ex:Edit un article)
In FF console: two errors
[10:07:28,345TypeError: $.browser is undefined http://mysite/modules/publisher/js/ui.core.js:13
[10:07:28,345TypeError: $.widget is not a function @ http://mysite/modules/publisher/js/ui.tabs.js:608


Link to publisher that i used



10
slider84
Re: XOOPS 2.5.7 Final Release Issues
  • 2014/6/19 8:39

  • slider84

  • Just popping in

  • Posts: 21

  • Since: 2013/8/16


Same issue in Publisher with xoops 2.5.7.
- Xoops default installation.
- Default theme.
- Default publisher installation.
No tabs for Publisher in administration section (Categories, articles...)




TopTop
(1) 2 »



Login

Who's Online

59 user(s) are online (36 user(s) are browsing Support Forums)


Members: 0


Guests: 59


more...

Donat-O-Meter

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

Latest GitHub Commits