? Failure

User tests: Successful: Unsuccessful:

avatar shur
shur
5 Sep 2014

If you export a live site's database and compare it to the core joomla.sql you'll see lots of minor differences. This hardens the database examination and shows that joomla.sql contains many code style mistakes.

avatar shur shur - open - 5 Sep 2014
avatar jissues-bot jissues-bot - change - 5 Sep 2014
Labels Added: ?
avatar brianteeman brianteeman - change - 5 Sep 2014
The description was changed
avatar brianteeman brianteeman - change - 5 Sep 2014
Category Code style
avatar nicksavov
nicksavov - comment - 9 Sep 2014

Thanks for submitting this, Shur! :)

The code looks good.

It's all code styling improvements, with the additions of the following two options for the postinstall_messages table:
IF NOT EXISTS
ENGINE=InnoDB

Looks like Travis is failing on the above two changes, so the unit tests would have to be updated appropriately.

avatar dbhurley
dbhurley - comment - 9 Sep 2014

@nicksavov Those failures are pre-existing and have been for several weeks now. :wink:

avatar nicksavov
nicksavov - comment - 9 Sep 2014

Ah, OK, cool. Thanks!

avatar nicksavov nicksavov - change - 12 Sep 2014
Status Pending Ready to Commit
Easy No Yes
avatar nicksavov
nicksavov - comment - 12 Sep 2014

RTC

This comment was created with the J!Tracker Application at http://issues.joomla.org/.

avatar shur
shur - comment - 18 Sep 2014

I don't know why my PR causes the Travis CI build mistake.
Is there any actions from my side expected to have this PR accepted?

avatar Bakual
Bakual - comment - 18 Sep 2014

There are some codestyle issues. You can see them at the bottom of https://travis-ci.org/joomla/joomla-cms/jobs/34492664. It would be great if you can fix those.

The failed unit tests itself are because we use a deprecated method in the tests. It hasn't anything to do with your PR. To fix that, you could rebase your PR with staging, if you know how to do that. Otherwise don't bother.

avatar elkuku
elkuku - comment - 18 Sep 2014

@Bakual This PR touches only one SQL file, so the code style errors are already present in the branch...

avatar Bakual
Bakual - comment - 19 Sep 2014

True, interesting :)

avatar shur
shur - comment - 26 Sep 2014

@Bakual

you could rebase your PR with staging

see the same PR in staging: #4311
and for Joomla 2.5 #4300

avatar phproberto phproberto - change - 8 Oct 2014
Labels Added: ?
avatar phproberto
phproberto - comment - 8 Oct 2014

This PR is not updated since the weblinks removal was updated in 3.4-dev.

@shur can you update/rebase it?

Thanks!

avatar phproberto phproberto - change - 8 Oct 2014
Labels Removed: ?
avatar jissues-bot jissues-bot - change - 8 Oct 2014
Labels Added: ?
avatar phproberto phproberto - change - 8 Oct 2014
Status Ready to Commit Needs Review
avatar shur
shur - comment - 8 Oct 2014

@phproberto
Frankly speaking I'm not sure how to rebase correctly.
But I made another PR #4311 that has all the changes from the current PR and much more changes. And that PR is associated to staging.

Probably the current PR can be closed, if PR #4311 is accepted.

avatar phproberto
phproberto - comment - 8 Oct 2014

@shur thanks but as this will be merged into v3.4 the PR has to be done against the 3.4-dev branch. You have to checkout that branch and then do your changes.

avatar shur
shur - comment - 8 Oct 2014

@phproberto

You have to checkout that branch and then do your changes.

I've compared these changes to the current joomla.sql from 3.4-dev.
This PR makes no sense now because all changes are already implemented by my another staging PR #4298

So I close it.

avatar shur shur - close - 8 Oct 2014
avatar shur shur - change - 8 Oct 2014
Status Needs Review Closed
Closed_Date 0000-00-00 00:00:00 2014-10-08 10:18:23

Add a Comment

Login with GitHub to post a comment