phpMyAdmin Planet phpMyAdmin

One of the problem I was facing last week has finally been resolved. In one of the issue, “Designer Save as enhancement”, earlier the changes were happening as expected but the problem was that it works only when we have a alert message. It doesn’t work without alert message(in last week, I wasn’t able to figure out why). Later on looking into the things, I figured out that there was a problem of synchronization here. To resolve this, I searched for a while and later on found .ajaxStop(). AjaxStop(): Register a handler to be called when all Ajax requests have completed. “Whenever an Ajax request completes, jQuery checks whether there are any other outstanding Ajax requests. If none remain, jQuery triggers the ajaxStop event. Any and all handlers that have been registered with the .ajaxStop() method are executed at this time. The ajaxStop event is also triggered if the last outstanding Ajax request is cancelled by returning false within the beforeSend callback function”(Source: https://api.jquery.com/ajaxStop/). Finally I created a PR to resolve the issue correctly.

Another problem which I was facing was with the issue “Designer should remember expanded/collapsed state”, here I don’t know exactly why I am not able to restore the states. Here the GET and SET values are correct and also I loaded the data into the appropriate variables correctly too, not sure where is the problem exactly. Still trying to figure it out.

Beside these 2 issues, I started working towards other 2 issues:
- “Designer should show tables from other databases by default”
- “Designer page save fails if dB name contains period .”

Regarding the issue, “Designer page save fails if dB name contains period .”, I remember that I was able to reproduce this while preparing the GSoC proposal but now I am not able to reproduce this. I have commented the same on the issue too. Let’s hope we figure this out as soon as possible.

Regarding the other issue “Designer should show tables from other databases by default”, I have looked at the discussions and code related to this(actually the discussion which lead to this issue) also, I am able to reproduce this one but not able to track this down(the point where we need to make the appropriate changes to resolve this).

In the upcoming week, I have to resolve these issues and discuss things with mentors if I face any problems. Also, I need to look at the refactoring work if I need to make any changes over there or not. I need to speed up the things as the deadline for the final evaluation is approaching and the work should be finished with complete documentation before that. Let’s hope I finish things on time.

Converted the ul’s on the top of some pages to navs.
Also worked on the top bar of the pages.
Added more commits to the earlier opened PR’s of tables, forms.
With these, I have dealt with most of the elements. Now, will look at the final improvements and required changes.
The PR related to the navs class is:
-> https://github.com/phpmyadmin/phpmyadmin/pull/15419

Last to last week we had our phase-2 evaluations and with the help of mentors, I successfully passed in the evaluation. For this evaluation, I thank to my mentors Isaac Bennetch, Deven Bansod, Saksham Gupta and William Desportes.

My mentors review was:
“ You’re continuing adequately with the project. You continue to produce code that is consistent with my expectations. In the past week, your communication has improved as we approached the deadline. Remember that regular blog posts are how the community and the group of mentors follows your progress, so stay on top of them, and even if a portion of code is undergoing review, further decision, or hasn’t yet been merged there should be other areas to work on. Keep pushing through and remember that the community has insight to help if you get stuck or need guidance. William and Saksham are both great resources aside from your mentor who are quite interested in the work you’re doing.”

From phase-2, I realized that I was late in posting blogs during the phase-2 coding period and I want to improve over this during the phase-3 coding period. By this way, mentors would have a idea about my progress, challenges I am facing, and how am I approaching the issues.

For the upcoming phase, firstly I have to resolve all the queries(if any) mentors had during the phase-2 evaluation and later on I have to resolve 4 existing issues which I have mentioned in my GSoC proposal(has the possible approach too) too. I will try to keep my last few day free so that I could give the things a final touch wherever needed. Here is the list of the issues to be resolved:
- Designer should remember expanded/collapsed state
- Designer should show tables from other databases by default
- Designer save as enhancement
- Designer page save fails if DB name contains period

In the 1st week of the 3rd phase, I first started with debugging the code written for the issue “Designer should remember expanded/collapsed state” and submitted with this PR. Issue firstly here in this PR was that it wasn’t populating the tables correctly after making changes(mentor Saksham Gupta mentioned this in the comments of the PR, later on I observed the same in the incognito tab where it doesn’t store any cache). For this issue, rather than considering all the tables at firstly, I made changes for one of the table and printed the GET and SET values in the localStorage. The values stored are the same but still it isn’t restoring the, not sure why. I have shared the screenshots and the code(with changes) for the same too at the comment section in the PR created. Also, I would like to suggest to refer to the PR for better insights.

Other than this issue, I started working on one more issue which is “Designer Save as enhancement”. To resolve this, I first inspected the elements which should trigger the changes and get to know their ID’s. After this, I tried to figure out the location where the changes are required to be made(Saksham Gupta’s PR on the same issue from the last year helped me here). After getting an idea about the code that will make it work, I added that code in the move.js file of the designer. I don’t know exactly why it’s not working if I remove one of the alert message(alert(‘yoo1’); in the screenshots available). Screenshots related to the same(look at the description of all the images for details about each step):

As requested “A Designer enhancement would be in the Save As page: we can automatically toggle the radio button to “Create a page and save it” when the use clicks the bottom text box.” the changes were happening but if we remove the alert(‘yoo1’); line, it’s not working the same way. Not sure exactly why right now.

For the upcoming week, I have to:
- write a blog post
- try to figure out exactly whats the problem here with both of the issues which we are trying to resolve
- Update mentors on a regular basis about the work

Table classes have been added to the remaining pages of pma.
Done with applying form related classes to elements of forms like ‘form-control’ to ‘legends’ and ‘select’ , ‘form-check, form-check-input, form-check-label’ to the ‘divs, checkboxes, associated labels’ respectively , etc.
The work can be seen in the following PR.
-> https://github.com/phpmyadmin/phpmyadmin/pull/15400

I completed with applying the table classes across all the server pages and making the required/relative css changes too.
The following PR was made.
-> bootstrap table classes added to all classes
Next, I begin with adding form classes and adding table classes to other pages than server.
A PR related to form classes will be soon opened by me.

I completed adding card classes to all the remaining pages.
Next main elements that I found on the pages were forms and tables.
I started working on tables and applied required classes to the tables across the pages.
This required changes in css also like need of the class “data” was completely eliminated.
So I also applied the required css changes altogether.

At the end of week-6, I have refactored move.js of the designer section partially and also completed the refactoring work for 2 other files(init.js and page.js). Since there were no reviews by then, I started refactoring rest of the code of move.js.

I have completed the refactoring of move.js by Tuesday(i.e. 16th July). Here I just need to replicate the changes which were similar to the work already done and mentioned in the blog post for week-6. Later this week, I have written and posted the blog posts for week-5 and week-6 which were due from a long time.

Once I was done with the refactoring work and documentation work, I have informed about these things to my mentor Isaac Bennetch and shared the relevant links with him. I have also asked for the reviews from Deven Bansod and Saksham Gupta.

By the time, I have also refactored other file, history.js. Devend Bansod pointed out the similar mistake which I have made in the phase-1 work, thus I need to make the similar changes over here too.

At this point, we have completed the refactoring work at least once(waiting for the reviews from the mentors). Also during this waiting, I double checked the syntax's which were mentioned in the blog post for week-6 and checked if all the changes made are good to go or not.

Rather than waiting for the reviews, we started working on one of the issues mentioned for the phase-3 work. The issue was “Designer should remember expanded/collapsed state”. For this, the proposed solution(in my GSoC proposal) was to use the localStorage(Stores data with no expiration date, and up to 5MB per origin). I started reading about the localStorage in a bit detail, during this I came across a doubt: Difference between window.localStorage VS localStorage. An article on Stack OverFlow has this solution which resolved my doubt.

Once I was aware of the working of the localStorage, I started searching that how and where do I need to make changes such that this issue can be resolved. For this I started a local server and opened the designer section for one the local database available. On the designer section of that database, there are different expanded and collapsed states like:

Here the arrows on the top left of each of the table represents the expanded/collapsed state.
“>” denotes Collapsed state
“v” denotes Expanded state

I inspected these icons on the browser and get to know the id associated with these. With help of this id, I tracked(using the id: “id_hide_tbody_”) the relevant code from where the job for expanding and collapsing is handled(read and observed the code around this id. Also, I confirmed this by printing a few things using console.log()). Currently, my next job to resolve this issue is to figure out how and where I can use the localStorage over here.

This is the code snippet related to the section from where the expanding and collapsing is done:

Summary of work related to the phase-2 is:
Commits in the following PR’s:
- https://github.com/phpmyadmin/phpmyadmin/pull/15378
- https://github.com/phpmyadmin/phpmyadmin/pull/15382
- https://github.com/phpmyadmin/phpmyadmin/pull/15345
- https://github.com/phpmyadmin/phpmyadmin/pull/15339
- https://github.com/phpmyadmin/phpmyadmin/pull/15318
Blog post other than this are:
- https://medium.com/@ikurimohit/gsoc-pma-week-5-fafb4c865e2a
- https://medium.com/@ikurimohit/gsoc-pma-week-6-31cba43a775a

Other than this as informed, I am working on the issue #12286 which is “Designer should remember expanded/collapsed state”. Also since there are still 2 more days remaining for the phase-2 coding period, I will update the work for that in this blog only.

UPDATE FOR LAST 2 WORKING DAYS OF PHASE-2:
As informed, I was trying to resolve issue #12286. For this I have opened a PR as of now. For this, I need to go through a few of the articles related to the localStorage so that I could know about its syntax and its other properties. At first I got stuck at a lot of points but later on, things started making sense and I was able to track what happens first(I need to print a lot of things and track them so that I could know which function is called upon a particular action). There is a function “smallTab” from where all the expanding and collapsing is done. This function was called using AJAX calls and that is where I stored data in the localStorage. To retain the state, I restored the data stored in the localStorage in the main function of the move.js file. To make sure this works,I printed a lot of things on the console and checked them multiple times but I am still unable to figure out what’s the exact issue here. For once, I have opened this PR so that if I am unable to figure out what’s the issue, someone from the community can point it out.

This was my 8th week of coding in GSoC and next would be second evaluation. My main task for the 8th week was to complete the composer package and host it as a stand alone repository along with completing my all previous work .

For the composer package, I wrote the package properties as composer.json and all functionalities in a well structured manner. The composer works completely stand alone of phpMyAdmin, stills gives status of configuration variables in a similar manner. Also I added tests so that the package can be directly tested in the terminal rather than only in the browser.

After discussing with my mentor, I am hosting it on phpMyAdmin’s github as a separate repository.

I will add the repository link and setup steps to this blog soon.

GSoC PMA week 7: Implementing Go-To Navigation

As per my project proposal my this weeks’ task was to start planning and working on my next task, which is to create a separate composer package having the phpMyAdmin’s mysql recommendation configurations. But since some of my last week’s task was remaining I also had to cover that.

I started with writing the backend functionalities for the navigation tab. Which included fetching and rendering of the tables and databases in the view. Integrating KBsearch using AJAX requests for realtime filtering and lastly linking various tables and databases to their views.

Finally the functional Navigation panel was achieved.

Also the search worked correctly and seamlessly.

Then I started with working on the composer package. I decided what all configuration variables to include in it.

Then I created a basic structure of the package using composer init and started with writing the logic by this and was expected to complete this by the next week before the 2nd evaluation.

My this weeks task was to implement the navigation panel as planned last week. I started with placing it in the top nav menu and creating a separate controller and view for the navigation tab. My next task was to write the functionalities for the controller.

Unfortunately, I felt ill this week and was suffering from conjunctivitis so was not able to work further.

So I decided to shift this next week along with the other task planned to be done in the 7th week.

It’s been a week since, the first evaluation. I’ve successfully passed the first evaluation. My task for this week was to work on adding a completely new feature in the phpMyAdmin portal. It is to provide them with a navigation panel so that different views can be easily accessed when ever required because sometimes the server has many tables, databases and other configuration and setting pages, it sometimes becomes difficult to navigate through for the user. So the feature is intended to provide them a better experience while working.

I started with planning out how the navigation panel is to be implemented, which included placement of navigation tab, list of views to be added for navigation, icon for navigation tab, working of search filter etc.

I came up with the following solutions for these:

Placement: I decided to keep it in the top menu bar as it would be most easily accessible there.

List of views: Initially I added all the databases and tables in the list. Other views can also be added easily as and when required.

Search Filter: I decided to use the KBFilter already used at many places in PMA.

Finally, the results for the phase-1 evaluations were out and I successfully passed. Thanks to my mentor Isaac Bennetch for reviewing my work and providing feedback at regular intervals.

Now for the upcoming weeks and Phase-2 work, we will firstly resolve and make the possible changes if any for the work submitted for the phase-1. Once done, we will move ahead with the refactoring and improving the file move.js of the designer section. Also, before phase-2 evaluations, I need to complete all the refactoring and improving work related to the designer section. Also, as planned, we need to resolve some issues which are already there in the designer section for the phase-3 work so it's good if we finish the refactoring work till phase-2.

That’s all the planning, now let's talk about the work done in the 5th working week of GSoC with PMA. During this week, as per reviews, one of the mentors Deven Bansod pointed out a great point which is:
while refactoring, I was changing document.getElementById(‘query_Aggregate’).style.display = ‘none’; to $(‘#query_Aggregate’).style.display = ‘none’;
There are a few things which were wrong with this like,

• I was missing the difference between jQuery Object and DOM element. The difference is that, $(‘#selector’) returns an array of the objects whereas document.getElementById(‘selector’) returns the first DOM object that is matched with the selector.

There were a few links which I found which help me to understand this is:

• https://stackoverflow.com/questions/6974582/jquery-object-and-dom-element
• https://stackoverflow.com/questions/1442925/how-to-get-nth-jquery-element
• https://api.jquery.com/css/

During this week, I have just started refactoring move.js, so I made changes in the following format:
changed from document.getElementById(‘selector’) to $(‘#selector’)[0]
I kept rest of the things as same, i.e.
changed from document.getElementById(‘selector’).style.display = ‘none’; to $(‘#selector’)[0].style.display = ‘none’;

This is all the work done in the week-5, planning to create a PR soon related to refactoring of move.js with some partial changes so that mentors can review and provide feedback on the same so that once we are all on the same page after all the refactoring and reviews being resolved, I can easily replicate the same for the rest of the lines in the move.js.

As started the work in last week, I finally created a PR which has partially refactored move.js file(around +60, -60 changes were there). I made changes in the following format(for example):
Changed from document.getElementById(‘selector’).style.display = ‘none’; to $(‘#selector’)[0].style.display = ‘none’;
i.e. changed document.getElementById(‘selector’) to $(‘#selector’)[0] everywhere.

For testing purposes, I added an example to show that these kind of changes won’t fail and will work. Here is the example as mentioned in the PR:
Using document.getElementById(‘selector’)

After creating this PR, Deven Bansod commented:
“this would work for the elements selected with IDs only. I’d ideally use .css() method to set the styles instead of manually selecting the first element and setting the native properties. IMO (even though it works) this current approach sort of doesn't use JQuery's power at all.
Using .css() would auto-loop over all the selected elements, so would be easier to read when we're selecting based on input types, classes etc”
Further, one of the other mentor, Saksham Gupta supported this comment and added “Don’t try to hard-code things. As you’re trying to refactor the code, try to do it in such a way that would let other developers work on the code without much changes to your code. It gets extremely difficult to manage such things on such a large scale.”

With those comments, I finally got the good picture and started working towards this. Thus I started changing the things again, here are the type of changes I have done:

• From “document.getElementById(‘selector’).style.display = ‘none’;”
  to “$(‘#selector’).css(“display”, ‘none’);”
• From “document.getElementById(‘selector’).style.position = ‘absolute’;”
  to “$(‘#selector’).css(“position”, ‘absolute’);”
• From “document.getElementById(‘selector’).style.zIndex = ‘103’;”
  to “$(‘#selector’).css(“z-index”, ‘103’);”
• From “document.getElementById(‘selector’).style.visibility = ‘visible’;”
  to “$(‘#selector’).css(“visibility”, ‘visible’);”
• From “document.getElementById(‘selector’).style.left;”
  to “$(‘#selector’).offset().left;”
• From “document.getElementById(‘selector’).style.top;”
  to “$(‘#selector’).offset().top;”
• From “document.getElementById(‘selector’).style.left = value + ‘px’;”
  to “$(‘#selector’).offset({left: value});”
• From “document.getElementById(‘selector’).style.top = value + ‘px’;”
  to “$(‘#selector’).offset({top: value});”
• From “document.getElementById(‘selector’).width = value;”
  to “$(‘#selector’).width(value);”
• From “document.getElementById(‘selector’).height = value;”
  to “$(‘#selector’).height(value);”
• From “document.getElementById(‘selector’).style.width;”
  to “$(‘#selector’).width();”
• From “document.getElementById(‘selector’).style.height;”
  to “$(‘#selector’).height();”
• From “document.getElementById(‘selector’).offsetWidth;”
  to “Math.round(parseFloat($(‘selector’).outerWidth()));”
• From “document.getElementById(‘selector’).offsetHeight;”
  to “Math.round(parseFloat($(‘selector’).outerHeight()));”
• From “document.getElementById(‘selector’).checked”
  to “$(‘selector).is(“:checked”)”
• From “document.getElementById(‘selector’).checked = false;”
  to “$(‘selector).prop(‘checked’, false);”
• From “document.getElementById(‘selector’).offsetLeft”
  to “$(‘selector’).position().left + parseInt($(‘selector’).css(“marginLeft”))”
• From “document.getElementById(‘selector’).offsetTop”
  to “$(‘selector’).position().top + parseInt($(‘selector’).css(“marginTop”))”
• From “document.getElementById(‘selector’).innerHTML === ‘v’”
  to “$(‘selector).html() === ‘v’;”
• From “document.getElementById(‘selector’).innerHTML = value”
  to “$(‘selector).html(value);”
• From “document.getElementById(‘selector’).className = value;”
  to “$(‘selector).addClass(value);”
• From “document.getElementById(‘selector’).value”
  to “$(‘selector).val()”
• From “document.getElementById(‘selector’).className === value”
  to “$(‘selector).hasClass(value)”

I have tested all these on w3school. For testing, I have opened something in standard vanilla JavaScript with DOM objects on their Tryit browser and made changes as per jQuery and run the same thing. Thus there was no change in results before and after the changes were made, thus validating the syntax. Here is an example for one of the above situation:

Here looking for the appropriate syntax and validating them took me a lot of time. And finally after these things, I committed the changes with no more hard-coded things.

Also side by side, Deven Bansod commented and pointed out the same issues with the previous PR which were part of phase-1 work. Once when I was done with the partial refactoring of move.js, I have done and resolved the same for these files as pointed out by Deven:
- https://github.com/phpmyadmin/phpmyadmin/pull/15339
- https://github.com/phpmyadmin/phpmyadmin/pull/15338

So now, I will be waiting for the reviews from mentors. Once made all the requested changes, we need to replicate the same for the rest of the move.js file and history.js file. Also, need to complete the documentation work in the week-7 of GSoC.

As I’d decided with mauricio that I will apply bootstrap classes on the individual elements across different pages once I finish with the basic layout(grid structure), I’ve started working on that line.

I have applied form classes to the login page. The following PR addresses the same.
https://github.com/phpmyadmin/phpmyadmin/pull/15364

Bootstrap card classes have also been added to home page.
https://github.com/phpmyadmin/phpmyadmin/pull/15369

Nupur Agrawal

Mauricio and i discussed and he suggested me to work on a separate and a new branch gsoc-bootstrap .

I’ll do all my project work on this branch and will get it merge to the master at the end of project.

I continued implementing the bootstrap grid structure to further pages. That part was easy for pages like ‘variables’ but really tricky for some pages like ‘users’ as html is still not completely extracted from php files to twig. Also, there are pages for which parts of html are extracted to twig of templates and parts are still there in php files.

Nupur Agrawal

As this was the last week before first evaluation, I summed up with the work I proposed to do before my first evaluation, that is, forming a basic layout for all the pages.
I did the finally editions to the basic layout of the required pages and added some commits to my previously opened PR’s.
Next, I will move to implement bootstrap to various elements of these pages.

Nupur Agrawal

-> https://github.com/phpmyadmin/phpmyadmin/pull/15320

This PR contains bootstrap grid structure for ‘settings’, ‘exports’, ‘imports’, ‘charset’, ‘engine’, ‘replication’, ‘status’ pages.

Nupur Agrawal

I discussed with mauricio about how to start and implement the things and we decided to implement grid structure for all the pages first.
So I started with the login page and home page and got it worked out there.
-> https://github.com/phpmyadmin/phpmyadmin/pull/15298

->https://github.com/phpmyadmin/phpmyadmin/pull/15299

The main idea was to apply container class to the page_contents and then apply row and the col classes to the different element that it contains.
This will make the pages more responsive according to the different sizes and also, there will be no need to provide the elements css properties like padding, margins as the structure handles that part efficiently.

I have now completed 4 weeks of coding in GSoC and the first evaluation is under way. My main task for the 4th week was to make up for anything left or include any additional changes suggested. I spent most of the time refactoring my code, making changes as suggested by my mentor and other PMA members and documenting my experience till now for the 1st evaluation.

In these four weeks, the first task I did was to fix the theme generator tool which took 2 weeks. The next work was to create Favorite Database feature. The details about these two are present in my previous blogs. I also worked on adding comments to my code so as to make it easy to understand for other developers.

In the coming days I will be working on writing some documentations.

This is the last week of coding before start of first evaluations. This week is more of a make-up week with a lot of discussions with mentors so that we can complete the work for first evaluations with complete documentations.

After all these 4 weeks, all JavaScript files of designer other than move.js(the file with more than 2.1k lines of code, which will be refactored in phase-2) and all the documentations have been completed.

Documentations:

• [COMMUNITY BONDING] https://medium.com/@ikurimohit/google-summer-of-code19-with-phpmyadmin-refactoring-and-impoving-designer-9dfe9663cf4
• [WEEK-1] https://medium.com/@ikurimohit/gsoc-pma-week-1-e8ac589a4103
• [WEEK-2] https://medium.com/@ikurimohit/gsoc-pma-week-2-7311632612b4
• [WEEK-3] https://medium.com/@ikurimohit/gsoc-pma-week-3-d04d226bc338

Pull requests created in the due time:

• https://github.com/phpmyadmin/phpmyadmin/pull/15300
• https://github.com/phpmyadmin/phpmyadmin/pull/15314
• https://github.com/phpmyadmin/phpmyadmin/pull/15318
• https://github.com/phpmyadmin/phpmyadmin/pull/15338
• https://github.com/phpmyadmin/phpmyadmin/pull/15339
• https://github.com/phpmyadmin/phpmyadmin/pull/15345

In this week, I also discussed and asked about some suggestions about my work from my mentor, Isaac Bennetch. Review from my mentor were good and we are now ready to go ahead for our work of phase-2. Also, I have started working on the refactoring of the file move.js of designer(phase-2 work) and created a PR for the same this week.

This is all for this week, next week will be our phase-1 evaluations and if successfully passed, lets continue from here in the phase-2.

I have completed my 3rd week of GSoC. My task for this week was to begin with a new feature which is to provide an option to users to mark databases as favorites. So that they can be easily accessed when ever required because sometimes the server has many databases and it becomes difficult to manage for the user. So the feature was intended to provide them a better experience while working.

The feature is very similar to the existing favorite table feature. My job was to replicate similar functionalities for databases.

The main problem was to update the database’s favorite status without reloading the page. For which I used ajax requests to send data to the backend and in return the json response was rendered in the frontend.

I had to add a controller which included functions to handle addition, removal and viewing of favorite databases. Finally the feature was complete the functionality worked fine.

GSoC PMA week 1: The coding begins !!

It’s been a week since I’ve been working on my Google Summer of Code project with phpMyAdmin and my work for the first two week was to fix a very important tool in PMA, which is Theme Generator. The tool was build by my mentor himself as his last year’s GSoC project. The tool allows user to create their own custom themes seamlessly.

Recently PMA shifted all their theme’s styles from css to scss. Which stopped the working of the theme generator. The first two weeks of my GSoC project were dedicated to fixing the theme generator.

I divided my work into two parts. For the first week I decided to fix the theme generator page which has the colour-picker tool for the user to choose from, four type of colour palettes: Monochromatic, Complementary, Analogous and Triadic and other details of the theme to be filled by the user. It also consisted of a preview option. For the second week I decided to change the files generated by the theme generator for new themes to be compatible with new rendering system. Initially they were in .css.php format but now had to be converted to pure scss files.

When I started with my work, the broken theme generator looked somewhat like this.

It took a little time to understand the rendering system in PMA as the code is quite vast. My major work was to pass the php variables to sass file and use them as scss variables in pure scss files. I went through the styling of theme generator, which was css in (theme_generator.css.php file) and JS for colour picker and previewing. I changed the styling to theme_generator.scss file and made the theme generator pick up css from there and was finally able to get it rendered as required.

I’ve completed my second week of GSoC and the main task for this week was to change the files generated by the theme generator for new themes to scss files which were css files earlier. The files were generated dynamically through PHP code.

Initially when the theme generator generated css files after successfully creating a new theme, when the new theme was selected. The pages rendered like this

The main challenge was that the user selected variables were as PHP variables and were required to be passed to scss files. For this we used PHP files to dynamically generate the scss files by passing the variables as strings.

A lot of code needed to be changed in format though the logic was mostly same. I had to add couple of new controllers which governed file generation as well.

And finally the theme generator worked all well. And new custom theme can be generated now.

To resolve the issues(merging all those commits in a single one) which were there in the PR created last week, I learned how to squash and rebase(as suggested by my mentor). But still, while squashing I faced some other issue i.e. after I enter the command to squash 7 commit messages but I got 784 commits in the next window which we get after entering the command on the terminal. Since I couldn’t figure it out why was I getting this, I copied the code and made a separate PR. This PR doesn’t have any of those issues but the other few issues in this PR were the following ones:

• Travis builds error
• An issue with merging many lines into a single line. Finally, we divided it into a single line only but with the logical division which was existing earlier.

All these issues have been resolved as of now. In this PR, I have removed js with jQuery and merged multiple lines into a single one. Also, I have completed the documentation work until last week. Here are the links to the previous 3 blogs:

• https://medium.com/@ikurimohit/google-summer-of-code19-with-phpmyadmin-refactoring-and-impoving-designer-9dfe9663cf4
• https://medium.com/@ikurimohit/gsoc-pma-week-1-e8ac589a4103
• https://medium.com/@ikurimohit/gsoc-pma-week-2-7311632612b4

For the upcoming week, I will be refactoring and improving other JavaScript files(not move.js as the lines of code in this file is way too much) and also I will be documenting weekly report. Since we have our first evaluations from 24–28th June thus we will be finishing up with the things as soon as possible.

Google Summer of Code’19 with PhpMyAdmin — “Refactoring and Improving Designer”

I would like to thank Google for enabling students to participate in open source development through GSoC. Also, I am very happy to announce that I’ll be working with phpMyAdmin this summer on the project ‘Refactoring and Improving Designer’.

“ Code refactoring should not be done just because we can.”

When the designer section of phpMyAdmin was initially written, there was no jQuery. But now since it exists and due to the advantages of jQuery over JavaScript and it’s a necessity over here, we could make this section better by making use of jQuery[Refactoring] and also resolve the existing issues[Improving]. Also, this project will be beneficial for both the important stakeholders, i.e. developers and user community.

This project will be beneficial for both the important stakeholders, i.e. developers and user community.

Developers:

• It will simplify HTML document traversing, event handling, animating, Ajax interactions, etc. Also, it is very powerful and easy to use
• Since jQuery has been optimized thus, developers can do the same things in fewer lines of code.

Users:

• Reduced load time
• It will be more secure once we reduce the number of global variables and functions
• Existing issues faced and reported by the users will be resolved

Also, while refactoring we have to follow good coding practices so that a new developer won’t face a problem in understanding the code.

Currently, the designer contains the following 6 JavaScript files:

In this time period, I will be refactoring different JS files for the first 2 phases and will be resolving some issues in the last phases of the GSoC timeline.

Project Schedule

May 6 — May 26, 2019

• Bonding with the community
• Get more familiar with the designer section
• Discuss the approach proposed of both the refactoring and issues, improvise based on the discussion

May 27 — June 2, 2019

• Refactor “history.js”
• Testing

June 3 — June 9, 2019

• Document and verify it with the mentor
• Refactor other small sized files

June 10 — June 16, 2019

• Change things as per review
• Refactor all files other than “move.js”(2.1K+ lines of code)
• Test work on a regular basis

June 17 — June 23, 2019

• Documentation and testing
• Verify work from the mentor
• Complete and submit work for phase-1 evaluation

First Mid evaluation: June 24–28, 2019

June 29 — July 5, 2019

• Update the files based on reviews of mentor
• Start refactoring with “move.js” file

June 6 — June 12, 2019

• Finish refactoring of “move.js”
• Test it properly

July 13 — July 21, 2019

• Verify work
• Refactor and make it more readable
• Finalize whole refactoring work
• Document and test the complete work
• Submit work for phase-1 evaluation

Second Mid evaluation: July 22–26, 2019

July 27 — August 2, 2019

• Discuss and finalize the possible solution of all the issues with mentors

August 3 — August 9, 2019

• Submit PR for : #14945, #13371

August 10 — August 16, 2019

• Submit PR for: #13587, #12286

August 17 — August 26, 2019

• Makeup duration
• Complete all the remaining work
• Document and testing
• Submit final work product

August 26 — Sept 3, 2019

• Mentors Submit Final Evaluations
• Final results of Google Summer of Code 2019 (3rd Sept 2019)

I’ll be updating my weekly progress of the project on this blog.

During week-2, I have created my first PR history.js — improving performance targeted at “gsoc-db-designer” branch. It’s merged after a lot of issues and discussions. Some of the issues were:

• Merge Conflict: It was because I started my work with the master branch and not from the already created “gsoc-db-designer” branch. Variable names were also different in this branch as compared to the master branch.
• ESLint error: While making changes, I made a few changes at places due to which I got this error.

Finally, this PR is merged. In this PR, I have done some improvements like earlier, we were calculating the length of an array each time in a for loop but now we have stored the length of the array outside the loop and use this variable inside the loop. Thus improving the performance of the designer’s history section.

Also, in the same week, I have started and submitted work for the second PR(link to the PR which was closed due to some issues). Here in this PR, I have made some issues at the start and due to which this PR includes the commit messages of the first PR too.

For next week, I have to resolve these things and complete the rest of the work.

Earlier before the GSoC results, I had a conversation with my mentor and I got to know that project (Refactoring and Improving designer) is unlikely to come as a GSoC project this year as there was less number of mentors available during the coding period. Thus I created a PR related to this project so that at least I can push the work which I have planned. Here is a link to that PR( https://github.com/phpmyadmin/phpmyadmin/pull/15165).

Later when GSoC results were out and I got selected to work on this project, I have closed the previous PR and discussed how are we gonna work on this project.

Initially, I suggested — “I am planning to create a single PR for the whole refactoring work in the designer section. Good to go?” But later on discussion with a mentor Maurício Meneghini Fauth, we decided that we can create a separate branch “gsoc-db-designer” at upstream where I can create all my PRs related to the project. Its because we don’t think it(everything in a single PR) is a good idea, as it is very difficult to review such a big pull request. And thus, it is better to open small pull requests that can be merged into the master branch or into a new branch just for this.

So finally after this discussion, I have started my work towards my first PR for my GSoC work.

May 6, 11:30 pm, I went to the GSoC website, hit the refresh button and searched my name under the list of selected projects. My name popped up and I was over the moon and it took me a while to let it all soak in.

Hello everyone!

I’ve been selected as a Google Summer of Code developer for the year 2019. Over the Summer I’ll be working with phpMyAdmin on the project ‘General Improvements’ under my mentor Saksham Gupta.

phpMyAdmin is currently well equipped and widely used web interface for MySQL and MariaDB. It has an Intuitive web interface and support for most MySQL features like managing databases, tables, columns, relations, indexes, users, permissions, etc along with a number of other features.

Still, there are a number of improvements and new features that can be added in the current version of code. Though they do not hinder the user’s working, adding them would make the user experience more seamless and smooth. The aim is to make the code free of, and less prone to, bugs, and add features to further enhance the accessibility, adaptability, and user-friendliness.

Further, I would like to throw some light on how I went about contributing to the organisation and my application process.

After the list of organisations was introduced, I looked through the list to find organisations with a familiar technology stack and project aligned with my interests. phpMyAdmin was one such organisation. I had some prior experience with Open Source as I applied for GSoC last year too.

Firstly I went through their project ideas and one of the ideas caught my eye. It was ‘General Improvements’ project which included adding new features and fixing some critical issues in the current platform. It included:

Fixing Theme Generator: A tool to create custom theme.
Adding Favourites Feature: Ability to mark important database and tables.
Creating composer packages: phpMyAdmin configuration files as a composer package
and some other Bugs and improvements in the code.

I immediately decided to apply for this project. I started with scouring some bugs and fixing them, this not only supplemented my PHP knowledge but also helped me in understanding the huge code base, contributing guidelines, healthy development practices, quality of code expected, etc. and not to mention the hands-on experience of working on a real-time project for an international organisation under brilliant mentors.

I frequently interacted with the community on their Gitter channel or on github issues with questions about their products and they were helpful in guiding me throughout. At the same time, I tried to help other developers in the community with setting up the projects, reviewing their pull requests, failed builds, etc. Even though I wasn’t always aware of the solution, I always tried to look up the errors and go through the relevant documentation to solve them and this was a win-win situation because even I ended up learning a lot in the process.

I started with my proposal couple of weeks before the deadline and got them reviewed by the mentor a week before, made relevant changes and submitted the final proposal. I had to follow a fixed template provided by the organisation for the proposal.

After submitting my proposal, the next month majorly went into preparing and appearing for my end semester examinations, I kept contributing to the organisation and interacting with the community members and of course GSoC results were always on my mind.

And finally the result came in my favour and on 6th may I received the mail:

In the following blogs, I will document my experience working on the project and all that I learn in the process. :)

What you can probably spot from past posts on my blog, my open source contributions are heavily focused on Weblate and I've phased out many other activities. The main reason being reduced amount of free time with growing family, what leads to focusing on project which I like most. It's fun to develop it and it seems like it will work business wise as well, but that's still something to be shown in the future.

Anyway it's time to admit that I will not spend much time on other things in near future.

Earlier this year, I've resigned from being phpMyAdmin project admin. I was in this role for three years and I've been contributing to the project for 18 years. It has been time, but I haven't contributed significantly in last few months. I will stay with the project for few more months to handle smooth transition, but it's time to say good bye there.

On the Debian project I want to stay active, but I've reduced my involvement and I'm looking for maintainers for some of my packages (mostly RPM related). The special case is the phpMyAdmin package where I was looking for help since 2017, but it still didn't help from the package becoming heavily outdated with security issues what lead to it's removal from Buster. It seems that this has triggered enough attention to resurrect work on the updated packages.

Today I've gone through my personal repos on GitHub and I've archived bunch of them. These have not received any attention for years (many of them were dead by the time I've imported them to GitHub) and it's good to clearly show that to random visitors.

I'm still main developer behind Gammu, but I'm not really doing there more than occasional review of pull requests and merging them. I don't want to abandon the project without handing it out to somebody else, but the problem is that there is nobody else right now.

Filed under: Debian English Gammu SUSE

I've been publishing updates about Weblate on my blog for past seven years. Now the project has grown up enough to deserve own space to publish posts. Please update your bookmarks and RSS readers to new location directly on Weblate website.

The Weblate website will receive another updates in upcoming weeks, I'm really looking forward to these.

New address for Weblate blog is https://weblate.org/news/.

New address for the RSS feed is https://weblate.org/feed/.

Filed under: Debian English SUSE Weblate

Weblate 3.6.1 has been released today. It is a bugfix release fixing several issues reported after the 3.6 release.

Full list of changes:

• Improved handling of monolingual Xliff files.
• Fixed digest notifications in some corner cases.
• Fixed addon script error alert.
• Fixed generating MO file for monolingual PO files.
• Fixed display of uninstalled checks.
• Indicate administered projects on project listing.
• Allow update to recover from missing VCS repository.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

Weblate 3.6 has been released today. It brings rewritten notifications, user data download and several other improvements. It also sets depreciation timeline for Python 2 installations - after April 2020 Weblate will only support Python 3.

Full list of changes:

• Add support for downloading user data.
• Addons are now automatically triggered upon installation.
• Improved instructions for resolving merge conflicts.
• Cleanup addon is now compatible with app store metadata translations.
• Configurable language code syntax when adding new translations.
• Warn about using Python 2 with planned termination of support in April 2020.
• Extract special chars from the source string for visual keyboard.
• Extended contributor stats to reflect both source and target counts.
• Admins and consistency addons can now add translations even if disabled for users.
• Fixed description of toggle disabling Language-Team header manipulation.
• Notify users mentioned in comments.
• Removed file format autodetection from component setup.
• Fixed generating MO file for monolingual PO files.
• Added digest notifications.
• Added support for muting component notifications.
• Added notifications for new alerts, whiteboard messages or components.
• Notifications for administered projects can now be configured.
• Improved handling of three letter language codes.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

The translation-finder module has been released in version 1.1. It is used by Weblate to detect translatable files in the repository making setup of translation components in Weblate much easier. This release brings lot of improvements based on feedback from our users, making the detection more reliable and accurate.

Full list of changes:

• Improved detection of translation with full language code.
• Improved detection of language code in directory and file name.
• Improved detection of language code separated by full stop.
• Added detection for app store metadata files.
• Added detection for JSON files.
• Ignore symlinks during discovery.
• Improved detection of matching pot files in several corner cases.
• Improved detection of monolingual Gettext.

Filed under: Debian English SUSE Weblate

Weblate 3.5.1 has been released today. Compared to the 3.5 release it brings several bug fixes and performance improvements.

Full list of changes:

• Fixed Celery systemd unit example.
• Fixed notifications from http repositories with login.
• Fixed race condition in editing source string for monolingual translations.
• Include output of failed addon execution in the logs.
• Improved validation of choices for adding new language.
• Allow to edit file format in component settings.
• Update installation instructions to prefer Python 3.
• Performance and consistency improvements for loading translations.
• Make Microsoft Terminology service compatible with current zeep releases.
• Localization updates.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

Weblate 3.5 has been released today. It includes improvements in the translation memory, addons or alerting.

Full list of changes:

• Improved performance of built in translation memory.
• Added interface to manage global translation memory.
• Improved alerting on bad component state.
• Added user interface to manage whiteboard messages.
• Addon commit message now can be configured.
• Reduce number of commits when updating upstream repository.
• Fixed possible metadata loss when moving component between projects.
• Improved navigation in the zen mode.
• Added several new quality checks (Markdown related and URL).
• Added support for app store metadata files.
• Added support for toggling GitHub or Gerrit integration.
• Added check for Kashida letters.
• Added option to squash commits based on authors.
• Improved support for xlsx file format.
• Compatibility with tesseract 4.0.
• Billing addon now removes projects for unpaid billings after 45 days.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

wlc 1.0, a command line utility for Weblate, has been just released. The most important change is marking this stable and releasing actual 1.0. It has been around long enough to indicate it's stability.

Full list of changes:

• Marked as stable release.
• Added support for more parameters on file upload.

wlc is built on top of Weblate API, you can use it on Weblate 2.10 or newer, though some features might require more recent version. Of course you use it on our hosting offering. Usage examples can be found in the wlc documentation.

Filed under: Debian English SUSE Weblate

Weblate 3.4 has been released today. The most visible new feature are guided translation component setup or performance improvements, but there are several other improvements as well.

Full list of changes:

• Added support for XLIFF placeholders.
• Celery can now utilize multiple task queues.
• Added support for renaming and moving projects and components.
• Include chars counts in reports.
• Added guided adding of translation components with automatic detection of translation files.
• Customizable merge commit messages for Git.
• Added visual indication of component alerts in navigation.
• Improved performance of loading translation files.
• New addon to squash commits prior to push.
• Improved displaying of translation changes.
• Changed default merge style to rebase and made that configurable.
• Better handle private use subtags in language code.
• Improved performance of fulltext index updates.
• Extended file upload API to support more parameters.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

Weblate 3.3 has been released today. The most visible new feature are component alerts, but there are several other improvements as well.

Full list of changes:

• Added support for component and project removal.
• Improved performance for some monolingual translations.
• Added translation component alerts to highlight problems with a translation.
• Expose XLIFF unit resname as context when available.
• Added support for XLIFF states.
• Added check for non writable files in DATA_DIR.
• Improved CSV export for changes.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

Upcoming Weblate 3.3 will bring new feature called alerts. This is one place location where you will see problems in your translations. Right now it mostly covers Weblate integration issues, but it will be extended in the future for deeper translation wide diagnostics.

This will help users to better integrate Weblate into the development process giving integration hints or highlighting problems Weblate has found in the translation. It will identify typical problems like not merged git repositories, parse errors in files or duplicate translation files. You can read more on this feature in the Weblate documentation.

You can enjoy this feature on Hosted Weblate right now, it will be part of upcoming 3.3 release.

Filed under: Debian English SUSE Weblate

Weblate 3.2.2 has been released today. It's a second bugfix release for 3.2 fixing several minor issues which appeared in the release.

Full list of changes:

• Remove no longer needed Babel dependency.
• Updated language definitions.
• Improve documentation for addons, LDAP and Celery.
• Fixed enabling new dos-eol and auto-java-messageformat flags.
• Fixed running setup.py test from PyPI package.
• Improved plurals handling.
• Fixed translation upload API failure in some corner cases.
• Fixed updating Git configuration in case it was changed manually.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

Setting up translation components in Weblate can be tricky in some cases, especially if you lack knowledge of the translation format you are using. Also this is something we wanted to automate from the very beginning, but there were always more pressing things to implement. But now the time is coming as I've just made first beta release of translation-finder, tool to help with this.

The translation-finder will look at filesystem (eg. checked out repository) and tries to find translatable files. So far the heuristics is pretty simple, but still it detects just fine most of the projects currently hosted on our hosted localization platform. Still if you find issue with that, you're welcome to provide feedback in our issue tracker.

The integration into Weblate will come in next weeks and will be able to enjoy this new feature in the 3.3 release.

Filed under: Debian English SUSE Weblate

wlc 0.9, a command line utility for Weblate, has been just released. There are several new commands like translation file upload or repository cleanup. The codebase has been also migrated to use requests instead of urllib.

Full list of changes:

• Switched to requests
• Added support for cleanup command.
• Added support for upload command.

wlc is built on API introduced in Weblate 2.6 and still being in development, you need at least Weblate 2.10 (or use on our hosting offering). You can find usage examples in the wlc documentation.

Filed under: Debian English SUSE Weblate

Two years ago, I've taken over uTidylib maintainership. Two years has passed without any bigger contribution, but today there is a new version with support for recent html-tidy and Python 3.

The release still can't be uploaded to PyPI (see https://github.com/pypa/warehouse/issues/4860), but it's available for download from my website or tagged in the GitHub repository.

Full list of changes is quite small:

• Compatibility with html-tidy 5.6.0.
• Added support for Python 3.

Anyway as I can not update PyPI entry, the downloads are currently available only on my website: https://cihar.com/software/utidylib/

Filed under: Debian English SUSE uTidylib

Weblate 3.2.1 has been released today. It's a bugfix release for 3.2 fixing several minor issues which appeared in the release.

Full list of changes:

• Document dependency on backports.csv on Python 2.7.
• Fix running tests under root.
• Improved error handling in gitexport module.
• Fixed progress reporting for newly added languages.
• Correctly report Celery worker errors to Sentry.
• Fixed creating new translations with Qt Linguist.
• Fixed occasional fulltext index update failures.
• Improved validation when creating new components.
• Added support for cleanup of old suggestions.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

Weblate 3.2 has been released today. It's fiftieth release of Weblate and also it's release with most fixed issues on GitHub. The most important change is in the background - introduction of Celery to process background tasks. The biggest user visible change is extended translation memory.

Full list of changes:

• Add install_addon management command for automated addon installation.
• Allow more fine grained ratelimit settings.
• Added support for export and import of Excel files.
• Improve component cleanup in case of multiple component discovery addons.
• Rewritten Microsoft Terminology machine translation backend.
• Weblate now uses Celery to offload some processing.
• Improved search capabilities and added regular expression search.
• Added support for Youdao Zhiyun API machine translation.
• Added support for Baidu API machine translation.
• Integrated maintenance and cleanup tasks using Celery.
• Improved performance of loading translations by almost 25%.
• Removed support for merging headers on upload.
• Removed support for custom commit messages.
• Configurable editing mode (zen/full).
• Added support for error reporting to Sentry.
• Added support for automated daily update of repositories.
• Added support for creating projects and components by users.
• Built in translation memory now automatically stores translations done.
• Users and projects can import their existing translation memories.
• Better management of related strings for screenshots.
• Added support for checking Java MessageFormat.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

Weblate 3.1 has been released today. It contains mostly bug fixes, but there are some new feature as well, for example support for Amazon Translate.

Full list of changes:

• Upgrades from older version than 3.0.1 are not supported.
• Allow to override default commit messages from settings.
• Improve webhooks compatibility with self hosted environments.
• Added support for Amazon Translate.
• Compatibility with Django 2.1.
• Django system checks are now used to diagnose problems with installation.
• Removed support for soon shutdown libravatar service.
• New addon to mark unchanged translations as needing edit.
• Add support for jumping to specific location while translating.
• Downloaded translations can now be customized.
• Improved calculation of string similarity in translation memory matches.
• Added support by signing Git commits by GnuPG.

Update:

Weblate 3.1.1 was released as well fixing test suite failure on some setups:

• Fix testsuite failure on some setup.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

Weblate 3.0.1 has been released today. It contains several bug fixes, most importantly possible migration issue on users when migrating from 2.20. There was no data corruption, just some of the foreign keys were possibly not properly migrated. Upgrading from 3.0 to 3.0.1 will fix this as well as going directly from 2.20 to 3.0.1.

Full list of changes:

• Fixed possible migration issue from 2.20.
• Localization updates.
• Removed obsolete hook examples.
• Improved caching documentation.
• Fixed displaying of admin documentation.
• Improved handling of long language names.

If you are upgrading from older version, please follow our upgrading instructions, the upgrade is more complex this time.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

This week I updated the code style to fit some of the PSR-2 rules, refactored some files and upgraded to Twig 2, in addition to helping the GSoC students.

Issues:

• #14341 Fix bug reported on pull request #14305
• #14317 Extension removal

The post Weekly phpMyAdmin contributions 2018-W22 appeared first on mauriciofauth.com.

This week I made up for the additional hours I worked on in the previous weeks. I removed the $dbi global variable from several classes, in addition to helping the GSoC students.

Issues:

• #14305 Remove md5 twig extension

The post Weekly phpMyAdmin contributions 2018-W21 appeared first on mauriciofauth.com.

This week I enabled the strict type mode in all PHP files, fixed some bugs and reviewed pull requests, in addition to helping the GSoC students.

Issues:

• #14286 Fix central columns in-line edit bug
• #14231 #13893 issue fix Simulating queries produce unexpected results
• #14272 fixes broken links to icons in the setup page
• #14304 [5.0.0-dev] Strict mode php errors
• #13893 Simulating queries produces unexpected results
• #14119 fix: AUTO_INCREMENT error when only exporting table structure in database-level exports; issue #14066
• #14066 Export MySQL Table (only structure) AUTOINCREMENT error
• #14296 Enable strict mode in PHP files
• #14278 Central columns can’t be edited or deleted by multiple selection after single edit
• #14290 Enable strict mode in some classes

The post Weekly phpMyAdmin contributions 2018-W20 appeared first on mauriciofauth.com.

This week I fixed some bugs, reviewed pull requests, replaced some deprecated jQuery functions and added type declarations to multiple classes, in addition to helping the GSoC students.

Issues:

• #14280 Adapt html functions to Twig templates
• #13999 Incorrect CURRENT_TIMESTAMP DDL generated with MariaDB 10.2
• #14265 Issue #14019 fix: Allow parameter in AllowThirdPartyFraming
• #14019 Allow parameter in ‘AllowThirdPartyFraming’
• #14189 Remember table’s sorting broken in 4.8.0
• #14204 Remember table’s sorting broken in 4.8.0 issue: #14189 fixed
• #14067 IS NULL search operator produces no WHERE SQL with spatial fields
• #14068 SPATIAL fields with no unique index/autoincrement error when clicking
• #14121 View spatial fields as WKT doesn’t work
• #14125 Fix for issues with spatial fields
• #14266 HTML entity incorrectly displayed
• #14275 Revert modifications
• #14267 Require a polyfill instead of the cytpe extension
• #14249 Edit/Replace view: missing Go button
• #14263 Fix for missing go button in view edit, #14249
• #14177 Fixes bug #13968
• #13968 Data truncated error with current_timestamp().000000 and mariaDB 10.2
• #14260 Language does not change in 4.8.0.1
• #14261 #14260 Fixed configuration for DefaultLang and Lang

The post Weekly phpMyAdmin contributions 2018-W19 appeared first on mauriciofauth.com.

This week I fixed some bugs and reviewed multiple pull requests, in addition to helping the GSoC students.

Issues:

• #14202 Binary foreign key enhancement #13894
• #14255 Addapt getTableHeader to twig template
• #14258 Patch for #14257 CodeMirror hints hidden
• #14257 CodeMirror hints hidden in functions/procedures/triggers
• #14216 Fix XML Export fatal error and add Move columns preview SQL
• #14212 [4.8.0] XML Export from single table throws fatal error (PHP 7.2)
• #14155 Feature Request: Move columns preview SQL
• #14211 Duplicate hidden token input field issue solved
• #14166 Changes to make Get auto saved query and show this query here again button functional
• #14254 #14253 Git commit info not showing when the repository is a submodule
• #14209 Duplicate hidden token input fields
• #14253 Git commit info not showing when the repository is a submodule
• #14094 Fix bugs in SQL query restore after session expire
• #14163 Not showing default query on changing table
• #14148 Not showing previous query on clearing Codemirror and then clicking get saved query
• #14144 “Show this query here again” checkbox does not work
• #14118 SQL tab already has a query loaded
• #14093 No auto saved query everytime new sql page is loaded
• #13894 Binary foreign key enhancement
• #14128 [4.8 RC1] Show 2FA Secret next to QR
• #14154 Display the secret for 2FA – #14128
• #14141 Remove inline styles from Relation.php

The post Weekly phpMyAdmin contributions 2018-W18 appeared first on mauriciofauth.com.

This week I added type declarations to some classes, refactored the PhpMyAdmin\Dbi\DbiMysqli class to use the mysqli class and fixed some bugs.

Issues:

• #14244 Fixes some jQuery Migrate warnings
• #12373 Theme selection for future releases
• #14210 Add Metro theme
• #14213 getThemeUniqueValue error in master
• #14232 4.8.0.1: Colums hidden on low resolution display
• #14102 More Dropdown not fully visible
• #14199 UI Issue – date picker hides in scroll frame
• #14029 Horizontal scrollbar not visible
• #14193 Regression – Scrolling down messes up the fixed column names
• #14206 patch fixed for the datepickerui broken #14199
• #14196 Fix for ui regression issues
• #14228 #14049 issue fix Query builder doesn’t work when the selected column …
• #14226 #12772 issue central column attributes don’t get filled in
• #14169 Regression – Action Icons glitch in 4.8.0
• #14194 UI Issue – I have to scroll down, to be able to scroll horizontally
• #14165 Query builder doesn’t work when selected column is * #14049 issue fix
• #14049 Query builder doesn’t work when selected column is *
• #12772 Central columns attributes don’t get filled in
• #14073 Central columns attributes don’t get filled in #12772 issue solved
• #14179 Remove Inline Styles from Ruotines.php
• #14173 Fix for error when running prepared statements, #14162
• #14162 SQL parser error trying to run a prepared statement
• #14137 Tables stop at border
• #14135 Tables in designer don’t stop at border
• #14224 Use array_key_exists instead of in_array + array_keys

The post Weekly phpMyAdmin contributions 2018-W17 appeared first on mauriciofauth.com.

This week I added type declarations to some classes and added the Metro theme in the master branch.

Issues:

• #14175 Theme problem in 4.8 version
• #14208 Fix errors due to undefined variables

The post Weekly phpMyAdmin contributions 2018-W16 appeared first on mauriciofauth.com.

This week the phpMyAdmin began to require PHP 7.1 in the master branch. So I updated the dependencies and removed some PHP 5 code. I also refactored some classes by replacing the static methods with instance methods.

Issues:

• #13896 Bump minimum version to PHP 7.1 for phpMyAdmin 5.0
• #13919 Remove font size feature
• #13925 Remove font size feature
• #14186 Bump minimum version to PHP 7.1

The post Weekly phpMyAdmin contributions 2018-W15 appeared first on mauriciofauth.com.

Weblate 3.0 has been released today. It contains brand new access control module and 61 fixed isssues.

Full list of changes:

• Rewritten access control.
• Several code cleanups that lead to moved and renamed modules.
• New addon for automatic component discovery.
• The import_project management command has now slightly different parameters.
• Added basic support for Windows RC files.
• New addon to store contributor names in PO file headers.
• The per component hook scripts are removed, use addons instead.
• Add support for collecting contributor agreements.
• Access control changes are now tracked in history.
• New addon to ensure all components in a project have same translations.
• Support for more variables in commit message templates.
• Add support for providing additional textual context.

If you are upgrading from older version, please follow our upgrading instructions, the upgrade is more complex this time.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English phpMyAdmin SUSE Weblate

The Docker container for Weblate got several improvements in past days and if you're using it, it might be worth reviewing your setup.

It has been upgraded to Python 3 and Django 2. This should cause no problems as Weblate itself supports both for quite some time, but if you were extending Weblate somehow, you might have to update these extensions to make them compatible.

The default cache backend is now redis. It will be required in future for some features, so you will have to switch at some point anyway. The memcached support is still there in case you want to stick with current setup.

Cron jobs have been integrated into the main container. So you no longer need to trigger them externally. This save quite some pain with offloaded indexing and another features which rely on regular execution.

Another important change is in logging - all logs are now go to the standard output, so you will get them by docker-compose logs and other Docker management commands. This will make debugging easier.

Filed under: Debian English SUSE Weblate

Hosted Weblate provides also free hosting for free software projects. The hosting requests queue has grown too long and waited for more than month, so it's time to process it and include new projects. I hope that gives you have good motivation to spend Christmas break by translating free software.

This time, the newly hosted projects include:

• ASS Danmaku - firefox extension for downloading danmaku
• KeePass DX - KeePass implementation for Android
• Liberapay Everywhere - the official Liberapay browser extension
• Offline QR Code Generator - browser add-on allowing you to quickly generate a QR code
• Guake - drop-down terminal for GNOME
• Planner - Project and Task manager designed for elementary OS
• EasySSH - The SSH connection manager to make your life easier.
• Misskey - A Twitter-like SNS
• Starke Verben - Android Application to learn your strong verbs
• FMIT - Free Music Instrument Tuner
• Crappy Firetitle - A firefox extension allowing customisation of windows' title
• Piano Booster - a MIDI file player that displays the musical notes AND teaches you how to play the piano

If you want to support this effort, please donate to Weblate, especially recurring donations are welcome to make this service alive. You can do that easily on Liberapay or Bountysource.

Filed under: Debian English SUSE Weblate

Next release on Weblate roadmap is called 3.0 and will bring some important changes. Some of these are already present in the Git repository and deployed on Hosted Weblate, but more of that will follow.

Component discovery

Component discovery is useful feature if you have several translation components in one repository. Previously import_project management command was the only way to help you, however it had to be executed manually on any change. Now you can use Component discovery addon which does quite similar thing, however is triggered on VCS update, so it can be used to follow structure of your project without any manual interaction. This feature is already available in Git and on Hosted Weblate, though you have to ask for initial setup there.

Code cleanups

Over the years (first Weblate release was more than six years ago) the code structure is far from optimal. There are several code cleanups scheduled and some of them are already present in Git repository. This will make Weblate easier to maintain and extend (eg. with third party file format drivers).

User management

Since the beginning Weblate has relied on user management and permissions as provided by Django. This is really not a good fit for language / project matrix permissions which most people need so we've come with Group ACL to extend this. This worked quite well for some use cases, but it turned out to be problematic for others. It is also quite hard to setup properly. For Weblate 3.0 this will be dropped and replaced by access control which fits more use cases. This is still being finalized in our issue tracker, so if you have any comments to this, please share them.

Migration path

Due to above mentioned massive changes, migrations across 3.0 will not be supported. You will always have to upgrade to 3.0 first and then upgrade to further versions. The code cleanups will also lead to some changes in the configuration, so take care when upgrading and follow upgrading instructions.

Filed under: Debian English SUSE Weblate

Last week I refactored some classes by replacing the static methods with instance methods.

Issues:

• #14057 Login screen doesn’t appear in android native browser+chrome
• #14076 Enable columns names by default for CSV in issue #14007 solved
• #14007 Enable columns names by default for CSV exports

The post Weekly phpMyAdmin contributions 2018-W14 appeared first on mauriciofauth.com.