Last modified: 2014-11-14 01:09:45 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T75048, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 73048 - Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (which is supported by core)
Flow comments content isn't saved properly when using >= 5.3.3 but < 5.3.6 (w...
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-05 22:22 UTC by Chris Koerner
Modified: 2014-11-14 01:09 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
flow_tree_revision (208.26 KB, image/png)
2014-11-05 22:22 UTC, Chris Koerner
Details
flow_revision (167.99 KB, image/png)
2014-11-05 22:22 UTC, Chris Koerner
Details
mystery comments (235.61 KB, image/png)
2014-11-05 22:23 UTC, Chris Koerner
Details

Description Chris Koerner 2014-11-05 22:22:06 UTC
Created attachment 17045 [details]
flow_tree_revision

Parsoid is running happily. I can edit pages using VisualEditor without issue.

I can visit a Flow page and add a new topic or comment. However, upon saving I don’t actually see the content of the comment. Topic titles do show up.

I’m not a DB guru, but upon inspecting the flow-specific database tables I noticed some weird syntax in the fields. Maybe it’s my editor (Sequel Pro) or an encoding issue.

I turned on MW debugging and I see this message:

Warning: DOMDocument::saveHTML() expects exactly 0 parameters, 1 given in /var/www/html/w/extensions/Flow/includes/Parsoid/Utils.php on line 273

1.25wmf5, PHP 5.3.3, most recent head/master build of Flow, most recent build of Parsoid.
Comment 1 Chris Koerner 2014-11-05 22:22:39 UTC
Created attachment 17046 [details]
flow_revision
Comment 2 Chris Koerner 2014-11-05 22:23:27 UTC
Created attachment 17047 [details]
mystery comments
Comment 3 Matthew Flaschen 2014-11-06 00:38:54 UTC
What database engine are you using (MySQL, PostegreSQL, etc.)?
Comment 4 Matthew Flaschen 2014-11-06 00:42:00 UTC
Sorry, I should have checked your screenshots first.  I see it's MySQL.  The weird characters are the binary UUID values.  Basically, consider the ID an arbitrary blob of bits (it does appear in the UI, serialized, in some places, e.g. in Topic URLs).

I'm not sure why it's not working, though.
Comment 5 Erik Bernhardson 2014-11-06 00:42:42 UTC
The problem with DOMDocument::saveHTML is most likely our issue, it looks like that argument was added in php 5.3.6

Which version of php are you on?  I think we advertise support of 5.3.3, but we might need to bump that.
Comment 6 Erik Bernhardson 2014-11-06 00:45:34 UTC
Actually i didn't read close enough, you are on 5.3.3.  I'm almost certain the problem is that, and we will have to update Flow's minimum requirements to 5.3.6.
Comment 7 Matthew Flaschen 2014-11-06 00:49:20 UTC
Erik is right.  Core requires 5.3.3, so we have the option of keeping support for that or documenting requiring 5.3.6.  The former may be doable if it's not much work, but core will probably bump above that soon anyway.
Comment 8 Chris Koerner 2014-11-06 18:37:31 UTC
I just tested on a system with 5.6.1 - Flow works as intended.
Comment 9 spage 2014-11-07 19:03:12 UTC
https://www.mediawiki.org/wiki/Extension:Flow now documents Flow's php 5.3.6+ requirement. I'm proposing WONTFIX, although patches welcome.
Comment 10 Chris Koerner 2014-11-13 19:12:47 UTC
While this is incredibly specific to my situation, I would like to point out that PHP 5.3.3 is still the standard version provided with RHEL-6. Which isn't the latest version, but still supported by Redhat.

Again, I realize this extension is a WMF-focused endeavor, but it's too cool to not be used elsewhere. :)

I'm off to argue with my linux sysadmins on updating PHP. Wish me luck!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links