https://jira.astppbilling.org This file is an XML representation of an issue en-us 8.13.3 813003 14-01-2021 https://jira.astppbilling.org/browse/ASTPPCOM-414 ASTPP Community <p>This is the 3.6 branch with all the current fixes applied, APART from the ones I mentioned in glitter.</p> <p>Also:</p> <ul> <li>Remove all PHP short open tags</li> <li>Fixes all PHP warnings, so it can be run with php 7</li> <li>Much better error reporting, and all error reporting turned ON (so hopefully it never gets as buggy as it was again!)</li> <li>Support for MySQL 5.7 <ul> <li>Note this uses 01-01-1980 as a replacement for the (invalid) 00-00-0000 datestamp. The better way to do that is to allow NULL datestamps, which is partially done</li> </ul> </li> </ul> <p>This would be a good starting point for 3.7!</p> ASTPPCOM-414

Current WIP

New Feature Done Done Samir Doshi Rob Thomas Sat, 28 Apr 2018 06:50:58 +0530 Thu, 1 Apr 2021 18:57:01 +0530 Thu, 1 Apr 2021 18:57:01 +0530 0 0 <p>Most of the conflicts are either ^M repairs, or short-php-opens. I haven't looked too hard. Also, I haven't even checked if this code works, this was just getting my branch up to date with yours. There may be more commits coming.</p> <p>Hi <a href="https://jira.astppbilling.org/secure/ViewProfile.jspa?name=xrobau" class="user-hover" rel="xrobau">Rob Thomas</a> </p> <p>Thanks for the updates. <br/> Merge conflicts are there, are you planning to add more commits on this branch? </p> <p>The merge conflicts aren't really fixable, if you look through them, because they're differences in the entire file (eg, remove ^M's) or different ways of doing things. You get to pick what you want to merge 8)</p> <p>Github has a surprisingly good 'resolve conflicts' button.</p> <p>Alright. I will look at that.</p> <p><span class="error">&#91;image: Mailtrack&#93;</span><br/> &lt;<a href="https://mailtrack.io?utm_source=gmail&amp;utm_medium=signature&amp;utm_campaign=signaturevirality4&amp;" class="external-link" target="_blank" rel="nofollow noopener">https://mailtrack.io?utm_source=gmail&amp;utm_medium=signature&amp;utm_campaign=signaturevirality4&amp;</a>&gt;<br/> Sender<br/> notified by<br/> Mailtrack<br/> &lt;<a href="https://mailtrack.io?utm_source=gmail&amp;utm_medium=signature&amp;utm_campaign=signaturevirality4&amp;" class="external-link" target="_blank" rel="nofollow noopener">https://mailtrack.io?utm_source=gmail&amp;utm_medium=signature&amp;utm_campaign=signaturevirality4&amp;</a>&gt;</p> <h2><a name="BestRegards"></a>Best Regards</h2> <p>Samir Doshi<br/> <em>iNextrix Technologie</em><em>s Pvt. Ltd</em>.<br/> <a href="http://www.inextrix.com" class="external-link" target="_blank" rel="nofollow noopener">http://www.inextrix.com</a></p> <p><em>Disclaimer:</em><br/> The information contained in this communication is confidential and may be<br/> legally privileged. It is intended solely for the use of the individual or<br/> entity to whom it is addressed and others authorized to receive it. If you<br/> are not the intended recipient you are hereby notified that any disclosure,<br/> copying, distribution or taking action in reliance on the contents of this<br/> information is strictly prohibited and may be unlawful. Please notify the<br/> sender immediately and destroy all copies of this message and any<br/> attachments contained in it.</p> <p>On Thu, May 3, 2018 at 11:51 AM, Rob Thomas &lt;notifications@github.com&gt;<br/> wrote:</p> <p>&gt; The merge conflicts aren't really fixable, if you look through them,<br/> &gt; because they're differences in the entire file (eg, remove ^M's) or<br/> &gt; different ways of doing things. You get to pick what you want to merge 8)<br/> &gt;<br/> &gt; —<br/> &gt; You are receiving this because you commented.<br/> &gt; Reply to this email directly, view it on GitHub<br/> &gt; &lt;<a href="https://github.com/iNextrix/ASTPP/pull/414#issuecomment-386200966" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/iNextrix/ASTPP/pull/414#issuecomment-386200966</a>&gt;, or mute<br/> &gt; the thread<br/> &gt; &lt;<a href="https://github.com/notifications/unsubscribe-auth/AA6gceMQIbd3Pg7mGRGvt7fIiHZSe4WSks5tuqHhgaJpZM4TrLwM" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/notifications/unsubscribe-auth/AA6gceMQIbd3Pg7mGRGvt7fIiHZSe4WSks5tuqHhgaJpZM4TrLwM</a>&gt;<br/> &gt; .<br/> &gt;</p> <p>I'm not going to persevere with this pull request, as it's just getting more and more stale. Plus commits like <a href="https://github.com/iNextrix/ASTPP/commit/309a35a5f1bc2a8aa4fb44deff1cbf3103669528" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/iNextrix/ASTPP/commit/309a35a5f1bc2a8aa4fb44deff1cbf3103669528</a> where one file was randomly placed inside another (breaking all CDRs) really disheartens me.</p> <p>Hi Rob,</p> <p>That was unfortunate bug and I hope there will not be any other.</p> <p>How would you like to keep your branch running?</p> <p>On Sun 13 May, 2018, 4:33 AM Rob Thomas, &lt;notifications@github.com&gt; wrote:</p> <p>&gt; Closed <a href="https://jira.astppbilling.org/browse/ASTPPCOM-414" title="Current WIP" class="issue-link" data-issue-key="ASTPPCOM-414"><del>ASTPPCOM-414</del></a> &lt;<a href="https://github.com/iNextrix/ASTPP/pull/414" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/iNextrix/ASTPP/pull/414</a>&gt;.<br/> &gt;<br/> &gt; —<br/> &gt; You are receiving this because you commented.<br/> &gt; Reply to this email directly, view it on GitHub<br/> &gt; &lt;<a href="https://github.com/iNextrix/ASTPP/pull/414#event-1623360854" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/iNextrix/ASTPP/pull/414#event-1623360854</a>&gt;, or mute<br/> &gt; the thread<br/> &gt; &lt;<a href="https://github.com/notifications/unsubscribe-auth/AA6gcZxovK3PWXnNq4brRfs8lMMvjx61ks5tx2otgaJpZM4TrLwM" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/notifications/unsubscribe-auth/AA6gcZxovK3PWXnNq4brRfs8lMMvjx61ks5tx2otgaJpZM4TrLwM</a>&gt;<br/> &gt; .<br/> &gt;</p> Development External issue ID 414 Rank 0|i00b6v: