6.0.0-git
2019-04-23

[#12532] Adding link widget into portal page ends with FATAL error
Summary Adding link widget into portal page ends with FATAL error
Queue Trean
Queue Version Git master
Type Bug
State Duplicate
Priority 2. Medium
Owners
Requester uwe (at) d2ux (dot) org
Created 2013-08-04 (2088 days ago)
Due
Updated 2013-08-04 (2088 days ago)
Assigned
Resolved 2013-08-04 (2088 days ago)
Milestone
Patch No

History
2013-08-04 21:09:25 Michael Rubinsky Comment #3
State ⇒ Duplicate
Reply to this comment
Already fixed in Trean 1.0.2
2013-08-04 20:31:34 uwe (at) d2ux (dot) org Comment #2
New Attachment: horde_addLinkWidget.png Download
Reply to this comment
added screenshot to show, which selection is choosen, when the wiget 
was included into portal page
2013-08-04 20:29:08 uwe (at) d2ux (dot) org Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ Adding link widget into portal page ends with FATAL error
Queue ⇒ Trean
Milestone ⇒
Patch ⇒ No
Reply to this comment
Hello Team,

first of all thank you for your effort to develop Horde to a really 
mature open groupware system!

By installing the 5.1.0er releases on our server, we have encountered 
in the Portal configuration on a problem that was already solved in 
the ticket #12303.

It seems, that the Portal view already chrashes, when a "Link widget" 
is added:
{{Fatal error: require_once(): Failed opening required
'/var/www/vhosts/htdocs/d2ux.org/horde/trean/lib/Block/../base.php
(include_path='/var/www/vhosts/htdocs/d2ux.org/horde/lib:.:/usr/local/share/pear') in /var/www/vhosts/htdocs/d2ux.org/horde/trean/lib/Block/Bookmarks.php on line 
72}}

Following scenario reproduce the issue:
1. Change to Portal view
2. Click "Inhalt hinzufügen" ("Add content")
3. Choose widget position and select  "Lesezeichen:Lesezeichen"
4. Click "Hinzufügen" ("Add")

After adding the portal URL chrashes with upon error. A change reset 
is only via DB manipulation for the defined user possible.

Reading the change logs for the last Horde releases, this ticket is 
not mentioned. Is it possible, that the fix is currently only in Trunk 
available?

Thank you again for your support! Let me know, if you need more information.

Best regards,
Uwe

Saved Queries