-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot Save or Update Long Articles #16112
Comments
This comment was marked as abuse.
This comment was marked as abuse.
Raw html of content article now attached at text. This is the article as it currently is. Any modification and attempt to save produces the problem. |
This comment was marked as abuse.
This comment was marked as abuse.
I just tested on multiple systems using php 7.1.1 and php 5.6.30 and it saved with no problem at all |
PHP portion is subject to the whims of our provider - short term answer is no, cannot upgrade at present. However it is possible to upgrade in the future. |
This comment was marked as abuse.
This comment was marked as abuse.
So this means you are increasing the minimum requirements of Joomla 3.7.1 to php 5.6.30? |
No that means that Phil was expressing his personal opinion |
This comment was marked as abuse.
This comment was marked as abuse.
I also has no issue saving your text on 5.5.38 |
@brianteeman I accept @PhilETaylor opinion that backwards compatibility can suck. |
my point is that your problem is probably not purely php version related |
FWIW we left the door open to revisit this all the way up to 4.0 beta 1 being released, so there's a lot of time to revisit and rethink that. Personally, I don't see us keeping PHP 5.5 support given the way our numbers are moving, but dropping everything before 7.1 is borderline pushing our luck right now. |
its all interesting but off topic |
Yes, it is the size of the article that has this effect. in my not so old PC, it takes about 80 seconds to save the article Out of which the JFilterInput::cleanTags on the article text were about 75 seconds
Filtering code does not seem broken in this case,
maybe 2x or 3x slower or more ? (i do not know , i have not tested with J3.6.5 (maybe tomorrow), Article text is about 300KBytes with a lot of tags (and tag attributes?), and server is probably a bit slow |
Having same issues, with something special:
Feedback of some editors: It only appears when having special characters in the pagebreak content. Example: When changing the special characters like this: Special characters in other parts of the article are no problem so far! What's wrong there? |
This comment was marked as abuse.
This comment was marked as abuse.
@PhilETaylor However, I found out: |
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
Maybe, but it until update (from 3.6.5) there was no such problem!? However, what should I look for then? I mean, that specific call causes an 180s (and maybe "forever") endless loop for looking up the pagebreak thing. |
This comment was marked as abuse.
This comment was marked as abuse.
Right. Because in 3.7.0 an extra layer of code was added to our filtering system to better handle multibyte characters. Clearly this has come with performance issues, which we are trying to rectify. But we cannot simply just revert that change as it also had security implications. |
@mbabker |
@PhilETaylor I have added it back. Not sure what happened but I didn't remove it to begin with. |
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
Extract it to a separate issue but we need test cases covering the
filtering library in at least every setup that the default ACL/filtering
config give. If we're only testing the defaults we're missing a lot.
On Fri, May 19, 2017 at 4:35 PM Phil Taylor ***@***.***> wrote:
ok I give up at 4.5hours of debugging.
The problem is replicate-able by disabling editors, logging into the front
end as a PUBLISHER, and then using the string
<hr title="Äußerungen" class="system-pagebreak" alt="Äußerungen" />
attempt to save an article, the code gets into an endless loop - this is
NOT a performance thing, this is an endless loop.
[image: screen shot 2017-05-19 at 21 42 49]
<https://cloud.githubusercontent.com/assets/400092/26267526/86cc93d4-3ce2-11e7-9e9f-d3ee4c708fd2.png>
The problem is that the escapeAttributeValues method is meant to
- Escape < > and " inside attribute values
when in fact its wrongly interpreting the "" after some Äuß kind of text
as still being *within* the attribute value, instead of understanding
that the " is the *closing* tag.
It then goes into a loop.. until the php.ini max_execution_time is
reached. *This is not a performance issue, PHP version issue, it is
replicate-able on a PHP 7.1/Joomla 3.7.1/Mac - Its a endless loop issue*
It looks like some of the work done by @ggppdk <https://github.com/ggppdk>
in the escapeAttributeValues method is at play here. Maybe he would like
to comment on this and test it.
I cannot create a unit test to replicate the issue at the moment, as the
wrong filters run during unit testing, and not the filters a PUBLISHER has
when they save an article.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16112 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAWfoS9Q5rSVcEy8PJJOxU6afYV-PSdzks5r7gslgaJpZM4NfYuc>
.
--
- Michael Please pardon any errors, this message was sent from my iPhone.
|
I think I found a solution. Where to write a unit test code? Which method? |
Never mind, I created PR #16140 |
@PhilETaylor , thanks for ping me
Wrong ! , my PR, besides fixing the meaningless addition
PR #16140 made by @csthomas, proves my argument, the faulty code was not added by my PR, it prexisted, and PR #16140 does not revert any of my changes
Wrong ! (see PR #16140 again) escapeAttributeValues() runs regardless of which TEXT filters you have, you can add a test case to the unit tests
and cleanTags that calls it , will run regardless if filtering for administrator or for publisher
I hope you are not confusing the performance issue with the parsing issue |
I do confirm a huge difference when saving as a Manager or as a SuperAdmin even after merging #16140 php.ini settings |
Any further movement on this? Just in case, I saw that in another report that Jsitemap Pro Pingomatic was causing a problem. On this specific site, the only third party extensions are the two main Akeeba ones. |
@lynnfredricks please have a Look and Test on #16201 |
@franz-wohlkoenig I just tested with 3.7.2 and execution time is not improved enough. Error has changed through: Same article, just tried saving it. |
@lynnfredricks can you please post comment on PR on PR #16201 itself? |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/16112 |
closed ashaving PR #16201 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/16112. |
Steps to reproduce the issue
Create or duplicate a large article such as this:
http://www.silkypix.us/silkypix-supported-cameras
Try to save the article.
Expected result
Saved article, as had worked under 3.6.5.
Actual result
White page with:
Fatal error: Maximum execution time of 30 seconds exceeded in /home/XXXX/XXXX/libraries/vendor/joomla/string/src/phputf8/mbstring/core.php on line 41
System information (as much as possible)
PHP 5.6.29
Joomla 3.7.1
Additional comments
The symptoms of this were present in 3.7.0 and merged into another item. The other item was listed as fixed and CLOSED, but updating to 3.7.1 did not solve the problem.
The text was updated successfully, but these errors were encountered: