Jump to content

MrPhil

Members
  • Content count

    8,105
  • Joined

  • Last visited

  • Days Won

    108

Reputation Activity

  1. Like
    MrPhil got a reaction from Smoky Barnable in Forum Changes   
    Harald, I have said it before, and I'll say it again:
    You cannot leave a product unattended for more than 12 months, or the ecommerce market declares it dead. You must have a major refresh or release at least annually, to stay in the public mind as a "current" product. The official product (currently 2.3.4.1) is the one that "one button" installers will pick up. That's the one that all newcomers will be using. It must be kept current. It doesn't matter if @burt's dazzling BS4 responsive PHP 7.3-ready plutonium-powered incredible edible edition is "available" on the main page -- that's not the one installers will pick. It would be best to take Frozen + patches and rebrand it as osC 2.5 (since 2.4 is already taken), and make it the official release. At least that will buy some time for a newer edition to be developed. If your work isn't ready by early 2020, Gary's BS4 edition could be 2.5.1, buying another year's grace. It's a very bad habit to not keep the current release updated, on the expectation that your work will be ready (Gold) Any Day Now -- history has shown that never happens, and these things slip for years. It doesn't matter how wonderful whatever you're working on will be -- it may well be the greatest thing since sliced bread, but if it's been more than a year since the last update, it will be starting from scratch in the public marketplace. In fact, it's worse than that -- it will have to first dig itself out of the "osCommerce is dead, dead, dead" hole before it's even in the race. Please declare everything earlier than (official) 2.3.4.1 to be immediate End of Life, and bar any further support discussion, except for how to migrate to the current version. 2.3.4.1 and Gary's CE works should go EOL in a year or so. Let's clear the decks of all the ancient stuff, and get everyone to the new 2.5 (a.k.a. Frozen) and eventually to whatever you release. Yes, tools are needed to make migrations less painful. If this feels like a bucket of ice water poured over your head, it's meant to be. Time to wake up!
  2. Like
    MrPhil got a reaction from Smoky Barnable in Transactional email service   
    I think we've got 2 or 3 different issues mixed together here:
    Excessive volume of emails (exceeding host's per-minute, per-hour, per-day caps). You need to find out from your host what the limits are. Unless they are ridiculously low, or your site is very, very busy; routine emails such as order confirmation should not be a problem. Newsletters and other such mass-mailing rates have to be low enough to not to interfere with routine emails. It's possible that you will need to use an external service to handle newsletters and other mass mailings. Newsletters and other "not necessary" communications (mass mailings) have to be explicitly "opt in", to avoid legal problems and accusations of spamming. Don't forget in every mailing to right at the top remind the reader that 1) they had signed up to receive the communication, and 2) how to easily unsubscribe (without reporting your store as a spammer). If your host (or other systems, such as Yahoo or Gmail) are flagging the content of any of your emails as spam, you will need to adjust the wording and contents to pass the spam tests. Certain words, certain phrases, an excessive number of links, etc. might have to be changed.
  3. Like
    MrPhil got a reaction from valquiria23 in Domain change, SEO and new oscommerce site version   
    Can you show us the full .htaccess file on both sites, and which directory they're in? ***-out any sensitive information. You don't have anything on your new site redirecting back to the old site, do you? Your description of what is happening is very confusing. Is this happening on the old site or the new site? If it's on the new site, it should have nothing to do with the redirection from the old site. Are both sites on Apache servers, or did you change server types?
  4. Like
    MrPhil got a reaction from valquiria23 in PayPal App v5.018 Log In with PayPal is now dead   
    Pete, "Frozen" has PayPal Pro built in -- it doesn't use the paypal-app you linked to. However, it's at 5.010, so my concern is whether you need to install, configure, upgrade, and then apply the patches above, or if the Frozen files could be updated ahead of time (via my Frozen patch). The best would be to update Frozen (via patches) to PayPal 5.018 so that when installed, it's there (along with the patches above). No further manual operations for the store owner. I will try to find a Frozen implementation that's been updated to 5.018, and compare files, and see if I can first update my Frozen patches to 5.018, then apply the patches found above. That would be the most desirable thing for anyone using Frozen.
    Update: I've started looking at the PayPal app vs. what's in Frozen. A lot of the differences in Frozen are trivial stuff -- use of $_GET/$_POST, __construct, hard coded file and table names, etc. However, it looks like Frozen is still at PayPal 4.039 while the app is 5.010. There are a lot of non-trivial differences between the two that will take some thinking about (which one is correct to use). Then, there is still the issue of various fixes proposed in this and other threads, and whether they can be applied to 5.010, and whether it's possible to upgrade Frozen to have 5.018 out of the box. (does the "upgrade" change the PHP files?) This is not going to be quick.
  5. Like
    MrPhil got a reaction from valquiria23 in Ezsocial for osC2.3.4BS v1.0a   
    Since Google+ has mostly gone away, should we be thinking about removing it from stores? I never used it, but my understanding is that it's only available for "G Suite", whatever that is. Do the Google+ functions on osC still do anything, or are they just an embarrassment that osC hasn't been updated in ages? If it should go away, I can add that to my Frozen patch set. It will be up to others to fix Edge and the official product.
  6. Like
    MrPhil got a reaction from valquiria23 in Confusion over osC Versions.   
    OK, Peter, let's draw a diagram:
    +--------------------------------------------------> osC 2.3.4.1 ------------------------------------> ??? | (official) basically suppress PHP 7 warnings osC 2.3.4 ---+ (official) | Gary Burton's now 2.3.4.1 +---- CE stream -----> Gold (snapshot) ---> known -----> changes -----> Frozen (snapshot)----> Edge continues on GitHub as Edge incorporated development BSv3 store only modularity, PHP 7 BSv4 both sides PHP 7.2 That, as I understand it, is more or less the history of osC over the last 4 years or so.
    Forget about "Gold". It's an obsolete snapshot. The "Frozen" snapshot is a quite stable, but needs a few patches. It is BSv3 (on the public store side only, not on admin). Gary has stated that he intends to make no further changes to Frozen -- that's what it literally is. He is working only on "Edge", with BSv4 responsive on both sides (store and admin), and some level of PHP 7.2 compatibility (eventually fully). It is a work in progress.
    There is no such thing as "Frozen BS4". It's either Frozen (with BS3) or Edge (with BS4), unless someone has their own private fork. In that case, they should make it very clear when discussing on this forum what they're talking about.
    Most people should use Frozen (plus patches), unless they want to be on the bleeding Edge of development. If what you want is a working store, I'd stick with Frozen. If you have the time and skills, and enjoy working with a constantly-changing code base, Edge could be for you.
    Yes, Frozen should be officially released as osC 2.5, but I'm not holding my breath. Yes, naming and versioning could be much improved by Gary, to reduce confusion. Only one repository is needed, as Gold and Frozen are fixed in time and space.
  7. Like
    MrPhil got a reaction from valquiria23 in modal info popup   
    I've run into problems with the popup manager. It would only edit or delete the first popup listed. I traced this to confusion in the code over when to use 'pID' and when to use 'popups_id' in the URL Query String (input and output -- it was a mixture of both). Basically, all popups_id= in building an href have to be changed to pID=, all $_GET['popups_id'] change to $_GET['pID'], and all '&pID=' in building a UQS apparently have to be just 'pID='. Leave $_POST['popups_id'] alone. Using pID consistently to mark which is the selected popup (for editing or deletion) seems to work.
    I'm still having problems with expired popups remaining active. Looking through the code, it looks like it is very confused in how it's implemented, like someone started with one train of thought and changed back and forth. For instance, the date_scheduled and expires_date get set to NULL, but status is still 1 (so it keeps being displayed). I'm not sure this setting the date fields to NULL when changing status was thought through all the way. I also have popups with a future expiration date having their expires_date field cleared to NULL for no apparent reason (possibly when clicking the "Activate" green button).
    I propose to change things a bit. status=0 would mean "not desired to be shown (by owner)", and status=1 would mean "desired to be shown". Instead of only 0 or 1 popups with status 1, any number could be 1. In cm_footer_pop_up.php, instead of playing with status when start/end dates are explicitly given, just loop through each status=1 popup (ordered by date_added, descending order). Check if date_scheduled (start) is NULL (started long ago) or in the past AND expires_date (end) is NULL or in the future, and output this popup. In popup_manager.php, the green/red light status change simply changes status to 0 or 1 for this one popup (doesn't affect others). The popups are again ordered by date_added, descending order. So, the first popup encountered in a specific order (most recently added to least) where status=1 (desired to show) and it falls within the given start/end dates, will be run. If an undesired one runs, the owner would have to temporarily deactivate the offending popup. In both cases, if expires_date is found to be in the past, status will be forced to 0. In neither case will start/end dates be changed to NULL.
    I think that this behavior would be closer to what a user would intuitively expect to see. What do you think (especially @Mikepo and @JcMagpie)? If Mike wants to update his add-on with the revised code, I can send it as a zip file once I've tested it and am happy with the behavior.
  8. Like
    MrPhil got a reaction from valquiria23 in Confusion over osC Versions.   
    OK, Peter, let's draw a diagram:
    +--------------------------------------------------> osC 2.3.4.1 ------------------------------------> ??? | (official) basically suppress PHP 7 warnings osC 2.3.4 ---+ (official) | Gary Burton's now 2.3.4.1 +---- CE stream -----> Gold (snapshot) ---> known -----> changes -----> Frozen (snapshot)----> Edge continues on GitHub as Edge incorporated development BSv3 store only modularity, PHP 7 BSv4 both sides PHP 7.2 That, as I understand it, is more or less the history of osC over the last 4 years or so.
    Forget about "Gold". It's an obsolete snapshot. The "Frozen" snapshot is a quite stable, but needs a few patches. It is BSv3 (on the public store side only, not on admin). Gary has stated that he intends to make no further changes to Frozen -- that's what it literally is. He is working only on "Edge", with BSv4 responsive on both sides (store and admin), and some level of PHP 7.2 compatibility (eventually fully). It is a work in progress.
    There is no such thing as "Frozen BS4". It's either Frozen (with BS3) or Edge (with BS4), unless someone has their own private fork. In that case, they should make it very clear when discussing on this forum what they're talking about.
    Most people should use Frozen (plus patches), unless they want to be on the bleeding Edge of development. If what you want is a working store, I'd stick with Frozen. If you have the time and skills, and enjoy working with a constantly-changing code base, Edge could be for you.
    Yes, Frozen should be officially released as osC 2.5, but I'm not holding my breath. Yes, naming and versioning could be much improved by Gary, to reduce confusion. Only one repository is needed, as Gold and Frozen are fixed in time and space.
  9. Like
    MrPhil got a reaction from peterbuzzin in Confusion over osC Versions.   
    I can't agree with Gary's reasoning on this. Since it's obvious that Harald will never legitimize Frozen as the official osC 2.5 (and later, some form of Edge as 2.5.1), it's time to stop bending Frozen to try to fit with the news and updates stuff. Just comment out all the code that interacts with updates and "latest version" items, and put up a "check GitHub here for latest version(s)." Or something like that.
    What developers keep losing track of is that most of the users of osC are business people, not computer nerds. It is unreasonable to expect them to dig through source files to find vague and confusing version stamps, and to have to remember the exact date on a zip file! They're just trying to run their business, and the more roadblocks we put in their way to making it relatively easy to manage their online store, the more of them will desert to easier-to-use platforms. What most want is a selling appliance, not a whole new career. The whole mess of ancient official versions (why in 2019 do we still have to tell newbies that they installed the wrong version?) and "Frozen with BSv4" fiascos couldn't be better designed by a competitor to sink osC.
  10. Like
    MrPhil got a reaction from peterbuzzin in Confusion over osC Versions.   
    I can't agree with Gary's reasoning on this. Since it's obvious that Harald will never legitimize Frozen as the official osC 2.5 (and later, some form of Edge as 2.5.1), it's time to stop bending Frozen to try to fit with the news and updates stuff. Just comment out all the code that interacts with updates and "latest version" items, and put up a "check GitHub here for latest version(s)." Or something like that.
    What developers keep losing track of is that most of the users of osC are business people, not computer nerds. It is unreasonable to expect them to dig through source files to find vague and confusing version stamps, and to have to remember the exact date on a zip file! They're just trying to run their business, and the more roadblocks we put in their way to making it relatively easy to manage their online store, the more of them will desert to easier-to-use platforms. What most want is a selling appliance, not a whole new career. The whole mess of ancient official versions (why in 2019 do we still have to tell newbies that they installed the wrong version?) and "Frozen with BSv4" fiascos couldn't be better designed by a competitor to sink osC.
  11. Like
    MrPhil got a reaction from Demitry in Database Optimizer   
    Keep in mind that it's more than just changing function names mysql_ to mysqli_. Some parameter lists in the calls will also be changed, so you need to check those.
  12. Like
    MrPhil got a reaction from valquiria23 in modal info popup   
    I got it working after comparing every file line-by-line. Something got munged moving the JS code in and out of template_bottom and other places. In the process, I found a few minor glitches:
    admin/includes/languages/english/popup_manager.php   line 27 indefinitely.. -> indefinitely.   line 49 glag -> flag admin/popup_manager.php  line 182  why is po.popups_id in the SELECT twice? Should one of them be pod.popups_id? I see pod.popups_id = po.popups_id in the WHERE clause. It seems to work as-is, but I think later versions of MySQL may get upset that pod.popups_id isn't listed in the SELECT clause. admin/popup_manager.php  line 228 includes class="ckeditor" on a textarea. I don't think that CKEditor is built in to Frozen. Is it harmless to leave it in that class, and you get some benefit if you happen to install CKEditor? includes/languages/english/modules/content/footer/cm_footer_popup.php   line 4  one every page -> on every page includes/modules/content/footer/cm_footer_popup.php  line 22  function cm_footer_popup(   ->  function __construct( install.txt  is misleadingly simple. After copying in the files, you need to go to Admin > Modules > Boxes > available boxes to install and order it to install the Popup Manager (or whatever it's called... it's gone now). You might note that nothing will show up in the installed Boxes list -- it goes into the Tools menu. Thanks to the (late) De Dokta, Mike, and Zahid  for their work on this.
    My client wants two things:
    Not only have a Close button, but also to automatically go away after 10 seconds. Does adding this after   $('#popupModal').modal('show'); in includes/modules/content/footer/templates/tpl_cm_footer_popup.php // disappear after 10 seconds setTimeout(function() { $('#popupModal').modal('hide'); }, 10000); look like it would do the job? Since popups would have varying amounts of information, maybe the time delay (10 seconds here) should be a parameter in the popup database entry. '0' second delay would mean "don't go away until explicitly dismissed" (and should be the default).
     
    Does this work cleanly on small devices? I'm wondering if a large image size would cause scrolling on a phone. I don't think customers would be pleased to have an important message disappear before they're done scrolling around the read the whole thing! Maybe it would be better just to stick to the Close button.
  13. Thanks
    MrPhil got a reaction from alex121121 in Change to EDGE from Frozen   
    You can keep your products, moving from any version of osC to any other, but you'll have to compare the database structures (schemas). It's likely that you'll have to massage the old DB to be structured the same as the new, a manual operation. When moving from one version to the next one up, SQL is often provided to do this for you, but I don't think there's anything for Frozen -> Edge. I don't think there are massive changes in the DB, but there might be a few.
    You are aware that Edge is a moving target (unstable -- a feature added today may be gone tomorrow)? Have you thought out why you want to leave Frozen and move to Edge? Is it worth the effort? Beyond the performance improvement of BSv4 support, I'm not sure there is that much changed. If you are having problems with Frozen, be sure to apply the patches (another manual operation; see link in my signature below).
  14. Like
    MrPhil got a reaction from pete2007 in Sent newsletter, now not recieving confirmation emails...   
    Your host ought be able to tell you if you're on some spam blacklist. They may even tell you that they added you because you sent out too many emails in a short period. They don't want their servers listed as spammers, either.
    It's fine to email newsletters from your shop's domain, but it should probably be left to a proper bulk email application that knows how to obey host limits for per-minute, per-hour, per-day mailings. It should also try to distribute evenly and at a polite rate to major email systems like gmail, hotmail, yahoo, etc., so they don't feel overwhelmed and report you as a spammer. Do you really need to get all 5000 emails out within one hour? How about over 2 days or so? Needless to say, all mass mailings must be explicit "opt in", and should include a reminder that the recipient signed up to receive them, and a reminder on how to easily unsubscribe. The latter two items reduce the chances that a recipient will report you as a spammer, simply to stop receiving mass mailings from you.
  15. Like
    MrPhil got a reaction from valquiria23 in Domain change, SEO and new oscommerce site version   
    Without logging visits to the old site (new code needed: maybe add something to the Query String during the redirect, and process it in new code at your new store), all you can do is guess how long people will continue to use bookmarks to the old site. Search engines should be gone within 2 or 3 months at most... maybe allow 6 months for people not to show up at the old site? Someone is bound to follow an old link or bookmark two years from now, but at some point you've got to cut your losses of maintaining a redundant site (cost of extra domain name registration, but you ought to be able to share hosting with the new store [see "add-on domain" on most servers]).
  16. Thanks
    MrPhil got a reaction from valquiria23 in Domain change, SEO and new oscommerce site version   
    Of course, that's on the old store's site, pointing to the new store site. If you've lost access to the old site, you're probably out of luck.
  17. Like
    MrPhil got a reaction from valquiria23 in Domain change, SEO and new oscommerce site version   
    If your products, SEO, directory structure, etc. are identical between the two sites, and the domain name is the only difference, it's very simple. In .htaccess,
    RewriteEngine On Rewrite ^(.*)$ https://<www.newdomain.com>/$1 [R=301,L] This assumes everything on the old site is to be sent over to the new site. If you want only part of traffic (to the old store) to be redirected, or the old store is in a directory of its own (a good idea), it would be done a bit differently.
  18. Like
    MrPhil got a reaction from Psytanium in PHP and MySQL upgrade for 2.3.4   
    1. Jumping code from PHP 5.4 to PHP 7.2 compatibility is a huge task. Even the bleeding edge Frozen and Edge work has barely started on it. They're both currently up to PHP 7.1, if you can roll back to that. If you want to do it yourself, I suggest you read https://www.php.net/manual/en/migration70.deprecated.php and for 71 and 72 as well. You might even have to take a look at 56, 55, and 54 migrations.
    2. Not really. The official 2.3.4.1 is merely 2.3.4 with the PHP 7 deprecated warnings turned off. Don't use it.
    3. No. The "upgrade" hits only a couple or so files, and is easy enough to do in-place. Just compare 2.3.4 and 2.3.4.1 files and you'll see. At best, turning off PHP 7 deprecated warnings will buy you a little time for a more permanent fix -- there's no telling what's not working right behind the curtain.
    One thing I hope you'll learn from all this is to keep your store on the current code base! This means carefully logging every single change you make to the files, what add-ons you installed, and very importantly, why you made a group of changes. There's no point in trying to replicate a bunch of code changes, only to realize half way through that Bootstrap responsive is already built in to the product! Whenever the pain of maintaining your current store's code base becomes too much, it's then easy to migrate to the latest and greatest, replicating all your new features without too much strain.
  19. Like
    MrPhil got a reaction from altoid in How do I use function __construct in this code?   
    They are  admin/includes/classes/payment_module_info.php (class paymentModuleInfo) and includes/apps/paypal/cfg_params/transactions_order_status_id.php (class OSCOM_PayPal_Cfg_transactions_order_status_id). Neither class seems to be invoked, so no harm done (yet). I don't know if it's better to add a dummy __construct(), or change the constructor name of these two.
  20. Like
    MrPhil got a reaction from valquiria23 in version with php7.2   
    It does, and I already checked. "MultiPHP" offered PHP 5.6, 7.1, and 7.2 until a few days ago. Now it's only 7.2. I get the feeling that someone panicked over some 7.1 vulnerabilities and killed 7.1 rather than wait for the next upgrade (hiding 7.1 in the meantime).
    Anyway, I'm looking at what needs to be done to get Frozen happy with 7.2. Just the built-in PayPal app is going to be a monster, merging Gary's changes (some of them for Bootstrap) with the later (5.010) edition in the app (and then various patches floating around and then maybe 5.018 level out-of-the-box). Then who knows how much needs to be done to the rest of Frozen. 😧
    I'd be happy to drop the whole project if I could be confident that a stable Edge with full BS4 and 7.2 upgrades and PayPal updated was just around the corner, but I'm not holding my breath. And who knows what Harald is working on... I just can't wait until something shows up there (if it ever does).
  21. Haha
    MrPhil got a reaction from René H4 in version with php7.2   
    Famous last words. My LP site just got banged when they dropped PHP 5.6 and 7.1 (which I was running on) last night and went to 7.2 ONLY. I just chewed out Support for not only doing this, but failing to notify me about the impending change. Anyway, it looks like getting patches for Frozen to run on 7.2 becomes a high priority, as I don't like simply suppressing "deprecated" warnings.
    Update: It turns out they did send emails headlining "5.6 being withdrawn" and saying that 7.2 would be the default and PHP 7 is the greatest thing since sliced bread. Nowhere did they mention that PHP 7.1 was also being withdrawn due to "severe security issues". Is anyone familiar with that? I'm willing to go to 7.2, but really got blindsided by their abrupt removal of 7.1 (which is still a supported version). Is this a real problem, or does this host have their head stuck where the sun don't shine?
  22. Like
    MrPhil got a reaction from puggybelle in Is there a way to make text or a symbol static in a form field?   
    If "parking" the currency sign just outside (before) the field isn't desirable, it might be possible to do it in Javascript. At each keystroke within the field, you'd check the string value, and if it's missing the currency sign in the right place, force it to be added to the string. This ought to work too for currencies that are after the amount.
    Is it critical that the currency sign be in the text field itself, or can it be added on later (in the PHP code processing the form input), if missing?
  23. Like
    MrPhil got a reaction from valquiria23 in Bootstrap Themes from WP or Opencart? Have someone try?   
    It sounds to me like a lot of people are looking for a "one button install" customization of their store to a given layout (call it a "template" or "theme" if you want). OK, how could that be done, without having to manually edit user.css, turn boxes on and off, etc.? I suppose some "template updater" thing could append some CSS to the end of user.css (rather than overwriting the whole file), import images, and update the database box entries to turn stuff on and off. Beyond that, is there anything else that can be done without editing "core" files? Maybe a "template" could auto-install certain add-ons? Beyond that, some "tpl" files might be overwritten or modified, but then we have to think about the possible consequences of this, with regards to updatability and maintainability.
    Auto update of user.css and box settings could take care of a lot of minor layout stuff, but to add new functionality (seen in a lot of "templates") is a whole new game. That could involve touching a lot of core files, but given the current architecture of osC, that may be unavoidable. At least, they could be essentially add-ons, and are therefore (in theory) removable.
    The next thing store owners will want is to regularly change among a number of themes, by holiday or season. Try to keep that in mind when designing anything. At the least, it should be a simple thing to back out the current template/theme and install a new one. Note that there might therefore be a "template.css" invoked just before "user.css". Done right, a seasonal update might be just a replacement of template.css.
    Is anyone familiar with how other themeable applications such as WordPress do it? Perhaps some ideas could be stolen from that.
  24. Like
    MrPhil got a reaction from Smoky Barnable in Forum Changes   
    Harald, I have said it before, and I'll say it again:
    You cannot leave a product unattended for more than 12 months, or the ecommerce market declares it dead. You must have a major refresh or release at least annually, to stay in the public mind as a "current" product. The official product (currently 2.3.4.1) is the one that "one button" installers will pick up. That's the one that all newcomers will be using. It must be kept current. It doesn't matter if @burt's dazzling BS4 responsive PHP 7.3-ready plutonium-powered incredible edible edition is "available" on the main page -- that's not the one installers will pick. It would be best to take Frozen + patches and rebrand it as osC 2.5 (since 2.4 is already taken), and make it the official release. At least that will buy some time for a newer edition to be developed. If your work isn't ready by early 2020, Gary's BS4 edition could be 2.5.1, buying another year's grace. It's a very bad habit to not keep the current release updated, on the expectation that your work will be ready (Gold) Any Day Now -- history has shown that never happens, and these things slip for years. It doesn't matter how wonderful whatever you're working on will be -- it may well be the greatest thing since sliced bread, but if it's been more than a year since the last update, it will be starting from scratch in the public marketplace. In fact, it's worse than that -- it will have to first dig itself out of the "osCommerce is dead, dead, dead" hole before it's even in the race. Please declare everything earlier than (official) 2.3.4.1 to be immediate End of Life, and bar any further support discussion, except for how to migrate to the current version. 2.3.4.1 and Gary's CE works should go EOL in a year or so. Let's clear the decks of all the ancient stuff, and get everyone to the new 2.5 (a.k.a. Frozen) and eventually to whatever you release. Yes, tools are needed to make migrations less painful. If this feels like a bucket of ice water poured over your head, it's meant to be. Time to wake up!
  25. Thanks
    MrPhil reacted to Harald Ponce de Leon in Forum Changes   
    @MrPhil thanks for the feedback. Our next announcements will address some of the points you have risen.
    @JcMagpie the topic must exist in the OSCOM v2.x -> Add-Ons forum channel. Could you confirm the location of the topic you're trying to link to?
×