6.0.0-beta1
7/6/25

[#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 08/04/2013 (4354 days ago)
Due
Updated 08/04/2013 (4354 days ago)
Assigned
Resolved 08/04/2013 (4354 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
08/04/2013 09:09:25 PM Michael Rubinsky Comment #3
State ⇒ Duplicate
Reply to this comment
Already fixed in Trean 1.0.2
08/04/2013 08:31:34 PM 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
08/04/2013 08:29:08 PM uwe (at) d2ux (dot) org Comment #1
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Trean
Summary ⇒ Adding link widget into portal page ends with FATAL error
Type ⇒ Bug
State ⇒ Unconfirmed
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