Timeline for Why is the recommended release of my module not proposed in Drupal updates?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14, 2015 at 19:18 | comment | added | Pierre.Vriens | Voilà, I recovered from the issue I encountered via the 7.x-2.1 version of the module. Refer to drupal.stackexchange.com/questions/161920/… (and the answer I added) for more details. Later on (tomorrow or so), I'll create an appropriate issue in your issue queue on D.O. For now "I call it a week", au revoir! | |
| Jun 14, 2015 at 18:55 | comment | added | cFreed | "Ca va" :-) I just got the "Please avoid extended discussions in comments" message, so I'll say nothing else for now. But sure I were very interested to exchange with you about some points, notably the "modules blank page", that I suspect to be a Drupal issue. | |
| Jun 14, 2015 at 18:32 | comment | added | Pierre.Vriens | "merci" for upvote! No problem about the various items you mentioned in your recent comments. I'm also a module maintainer (and know how it is like), check my profile for a 1st impression about "my" modules. Yes I'll create appropriate issue(s) on D.O for your module (soon). Right now I'm working on (temporary) "disable" of your 2.1 module in a Drupal-compliant way (without deleting the entire module dir). So give me some time to get back to you on this ... ça va? | |
| Jun 14, 2015 at 18:24 | comment | added | cFreed | FYI, several points: 1: I use to be closely concerned about any problem a user may experience related with my work. It's why I quickly began examining the successive issues you pointed out, so forgetting upvote BTW. 2: I only just noticed that your answer also stated a third problemn (the PHP warning). 3: for all that, may I propose you create an issue (or may be several ones), where we can exchange more comfortably than in those comments? TIA. | |
| Jun 14, 2015 at 18:06 | comment | added | cFreed | Oops (again!). Didn't pay attention to your 2nd comment, because I was immediately focused on the 3rd one. Yes, indeed, I agree that your answer is useful, so I just upvoted your answer, gladly. Please let me know if and how you could get rid of the "modules blank page". | |
| Jun 14, 2015 at 17:01 | comment | added | cFreed |
I'm sorry if I were the cause of your problem! I agree it could be related with the presence of my module, since it happened to me months ago. I never could understand what had happened (happened only on one site, while other ones worked fine with the same release), but got rid out of it merely suppressing the whole multilang folder (there is no database nor variables involved with this module). So you may consider using the same simple method. Also I just published 7.x-2.2 which fixes the bug you pointed.
|
|
| Jun 14, 2015 at 16:49 | history | edited | Pierre.Vriens | CC BY-SA 3.0 |
added 739 characters in body
|
| Jun 14, 2015 at 16:31 | comment | added | cFreed | Oops! What you pointed is a regression bug. I'd not detected it by myself because it ONLY happens at install time or when reading inline help, and I missed testing that again (shame :-). Besides that, nobody else opened an issue to report it, so thanks a lot for having alerted me about it. But I tend to think it's not the cause of my issue: first because this bug already existed in several earlier releases, and also because I can't figure out how the git<-->drupal.org mechanism might be aware of something which only regards the content of the release, no? Anyway, thanks again. | |
| Jun 14, 2015 at 14:25 | history | edited | Pierre.Vriens | CC BY-SA 3.0 |
added 208 characters in body
|
| Jun 14, 2015 at 14:15 | history | answered | Pierre.Vriens | CC BY-SA 3.0 |