Stay with jD 1.9 on Joomla 3.3 till final jD 3.2?

[Hans Karl]

Hello guys!

First of all I'd like to say thank you for your sustaining work on this brilliant component!

I have just done the migration from jD 1.9 on Joomla 2.5 to jD on Joomla 3.3.6. Basically everything works, but ...

After some looking around I found following problems:

1. old urls of category- and detail-pages are broken due to changed IDs - that's a really bad show stopper and needs to be changed
2. voting results are messed up: for some downloads they are missing while other downloads that never got votes no have some...
3. front-end layout is not responsive
4. jD css files include class names conflicting with t3 framework - resulting in minor styling glitches of e. g. the login module

Do you think these issues will be fixed in your final release?
Should I better stay with 1.9.x branch  - provided it's compatible with Joomla 3.3?

Thanks for your help!

[ColinM]

Hi
Item 1 is known that one has to re-make the links in articles.
Similarly that the voting results get wrong ids is known

Making the front end layout is not a jDownloads problem but one due to your chosen template.  Most widths are given in % terms and I find the result is responsive - it even works on my Android.  But if you know of a specific case please let us know.

Jdownloads CSS is readily changeable, again this might be a template challenge.  But as above if you have specific issues please let me know and I will look at it. 

Which particular Template are you using.  Is it from JoomlArt or JoomlaBamboo.  Is it just the T3 framework?

I am told that jD 1.9.2 series runs OK on Joomla! 3.3 series.  In your position I would make the transition from 1.9.1 series on Joomla 2.5 to J1.9.2 on Joomla 3.3 and then to jD 3.2 series.  That route appears to minimise challenges.  When you do this is of course your decision.

Presently the last major challenge is get the permissions to cascade. This is the most active area for Arno.  He is also anticipating making enhancements to the initial transfer script to iron out some of what you have noted.

[Hans Karl]

Hi Colin!

Thanks for your very quick reply.

I am delighted to hear that Arno is working on the issues I mentioned in point 1 and 2.

I am using the very basic T3 BS3 Blank Template with some adjustments. The conflicting class is "tip". It is used e. g. for the login module. Changing the jD css would not help alone. I am afraid I also had to hack the jD code to rename the class.

Well, for the time being I will stay with jD 1.9.2.11 beta which indeed works fine with joomla 3.3.6.

Any clue when jD 3.2 final will be released?

Thanks!

[ColinM]

The .tip css class is a standard jQuery class used to show tool tips in Joomla 2.5 and 3.x.  It is not a jDownloads Class but one has to use tip or tooltip as appropriate to style them. 

Below I have shown the relevant section of jdownloasds_fe.css concerned with tooltipsIt starts at around line 590

You could quite safely omit the first 3 styling lines shown as optional.  Only challenge is that you will need to do that on every jDownloads update.
You could also experiment with the other lines but they should not cause you a problem.  In any case the ones from jdownloasds_fe.css will only be apparent when you have jDownloads content on the page.

/* ++++++++++++++  .tooltip-inner for v3.x series ++++++++++++++ */
/* ++++++++++++++  .tip for v2.5 series ++++++++++++++ */
.tooltip-inner, .tip{
  /* optional styling  omit for tempate defaults*/
   border: solid 1px #ccc !important;
   background: #ededed !important;
   color:#000333 !important;
  /* +++ items below are essential */
   width: 250px;
   position: absolute;
   z-index: 2;
}
.tooltip.in, .tip-wrap{
  /* required to overcome opacity with tempate defaults*/
  opacity: 1 !important;
  filter: alpha(opacity=100) !important;
}
.tip-title {
  /* turn off arrow in 2-5 series as it is misleading on right hand side tooltips*/
background-image:url('') !important;
}

Our first and most important goal is to get a stable release.  It is close, the only major outstanding issue is handling the cascading of permissions.

You ask how soon, well as soon as possible is one answer.  Another is twice as long as half of it!  Basically solving a problem is an unknown quantity but I firmly believe it is this year.  Like a Christmas present perhaps!!

One aspect I will be dealing with is revising the css to make it more flexible.  Possibly in two parts, the essential part and the customisable part.  But I do not want to do that at this juncture as it would cause unnecessary delay.