Jump to content

MrPhil

Members
  • Content count

    8,156
  • Joined

  • Last visited

  • Days Won

    111

MrPhil last won the day on June 30

MrPhil had the most liked content!

Profile Information

Recent Profile Visitors

110,682 profile views
  1. FUD? BS! I'm not going to mention Phoenix in my sig, or promote it anywhere, if you're going to have an attitude like that.
  2. MrPhil

    Fatal error, webhost is stumped

    If it's the same issue, there's no problem that it's a few months old. The problem is hijacking old threads to start talking about a different problem. That becomes very confusing when the matter being discussed suddenly lurches to something else, and the subject (title) line no longer matches up.
  3. I don't think I should bother adding a mention of Gold, as it is so old. I will add that Frozen is sunset. Could you clarify what you've done with Edge vs. Phoenix? I was under the impression that Phoenix was a snapshot of Edge (as Frozen was), but this time with a series of patches to keep it updated, while Edge continues the development (but its use for production stores is discouraged, as it's too unstable). Or has Edge been renamed to Phoenix, or is it something else altogether? I'm just trying to visualize the family tree so I can understand what I'm giving links to. It doesn't help to sometimes call it Master and other times Phoenix. If someone wants to consider Phoenix from my siggy, I would assume that they want a full install (/tree/a.b.c.d). I'm not going to update my sig every time you have a point release, so where should I point them to find the latest and greatest (assuming they don't know at this point what the current a.b.c.d is)? Is there a /latest-full that points to the appropriate place? The alternative is to point them to the latest full release on the osC Products page, but then they have a bunch of updates to find and install. Is there some central repository of Phoenix incremental update zip files, or are they just scattered around this forum? Either way, keep in mind that most people looking for an installable are not computer nerds and need a lot of hand holding. You need to make it easy for them. Come to think of it, if they download 1.0.0.0 from the Products page, will they even be aware that there are numerous patches? One thing that occurs to me is that some people are going to see "osCommerce Online Merchant 1.0.0.3" (or whatever the name is), see there's an "osCommerce Online Merchant 2.3.4.1" on the Products page, and say, "Man, this one is way obsolete! I'm going with the latest and greatest, 2.3.4.1! Obviously it's much better..." Are the names distinct enough to avoid this understandable confusion? In one of your announcements, you state that the shop (public) side is now BSv4, but I thought I saw you state at one point that you were close to done with a responsive (BSv4) admin side, too. Did that go away at some point? Should the vast majority of potential users be at PHP 7.0+ by now, so you can afford to state that 7.0 is the minimum? I'm wondering how many PHP 5.6 (and even earlier) servers are still out there, that Phoenix may still run fine on. Is it worth having someone at PHP 5.6 pass up Phoenix because they think it won't run on their server?
  4. MrPhil

    newbie

    If you're just starting out, you're best off leaving the store in its own catalog/ or shop/ directory, and not in the site root. That way, you can easily add other subsystems (e.g., a blog, a photo gallery) in their own directories, with some sort of "landing page" in the root to direct visitors to the appropriate area. Any subsystem can then be changed or removed without the risk of breaking something else in the site (as happens when a store or other subsystem is mixed in with root files), and you won't have the complications of having your blog's URLs pass through the store's .htaccess or vice-versa. Until you bring up other subsystems and a landing page, you can tell the server to silently (200 status code) rewrite an incoming URL to your root over to the catalog/ or shop/, in /.htaccess. That way, visitors don't have to remember to type in "catalog/", and when you do add other subsystems, bookmarks and search engine entries won't have to change.
  5. It's a 500 (Internal Server) error, so check your site server log to see if there is any additional information. Something looks really messed up with the URL... the ? and & together (a term between them missing?), and the orderID that looks a lot more like a session ID (oSCId), unless that's a payment system-specific ID. Exactly what version of osCommerce are you using, where did you get it from, what PHP version is your site running on, what add-ons have you installed, what payment system(s) are you using, etc.? If you're just starting out, scrap your current "official" installation and install the Community-supported "Frozen" plus patches (see links below in my signature). It is responsive (mobile-friendly), truly PHP 7.1 compatible, has many other improvements, and is supported. Even if you've already entered a large number of products, it may be easy enough to transfer the database to the new installation (it will need updating). There is an even newer "Phoenix" release, but I would wait a few weeks before trying to use it, until the major bugs have been shaken out.
  6. Phoenix 1.0.0.2, not 2.0.0.2?
  7. Note that some hosts are refusing to offer anything earlier than PHP 7.2, so listing it as 7.1 could scare off some potential users. That said, it should not be listed as 7.2 or 7.3 compatible until someone has gone over it with some sort of checker (or checking process) to methodically confirm that there is nothing obsolete or deprecated still in the code. The base code should not require suppression of deprecated warnings, although various add-ons still might. Logging warnings to a file only the admin can see, and not the customers, is a good idea.
  8. I could see a brick-and-mortar store owner walking through the aisles, cross-checking on their phone what their e-site offers, and doing at least minor updates in admin. Therefore, it might not be so far-fetched to want to be able to do admin on a phone. Of course, they could also just jot down notes on a pad, and do everything back in the office.
  9. You can certainly display frame styles like any other merchandise. You can select lens types and treatments, but if that is not compatible with all frames, you might be facing some custom coding to show available frames for a type of lens. You would have to have a place to enter the prescription information, which would be passed on to whoever is cutting and shaping the lenses. Is that simple text, or are there complicated symbols (can a consumer be trusted to accurately transcribe an eyeglass prescription)? Pricing could get quite complicated if it depends on many factors. Finally, depending on where you are, eyeglasses may be regulated as medical devices, and require special certification for you to handle. TL;DR I'm sure it can be done, but probably not "out of the box" osCommerce -- it will almost sure require some custom work, more than just an add-on or two. Or was this just a spam attempt? (I see that links were removed by another moderator.)
  10. MrPhil

    Marketplace Category/Version Cleanup

    What's your point? The official osC 2.3.4.1 (found on every one-button installer) is not really PHP 7 ready (it starts having problems above 5.4 or so) and is non-responsive. The CE stream (Frozen/Edge/Phoenix) work with up to PHP 7.1, and are responsive. Plus, you get a lot of functional enhancements (such as improved modularity) along with the other things. I fail to see why it's better to put in all the work to upgrade an official site to PHP 7.x and responsive, when you could simply install something from CE and customize that with add-ons and CSS tweaking. If you made tremendous changes to your official osC store, and neglected to keep any record of what you did, well, you deserve the extra work. Even then, in the long run, it will be less work to start over from CE (looking at future upgrades).
  11. tep_output_string() appears to be cleanup for HTML display, not for correct URLs. I think it's been used incorrectly here for a long time.
  12. So what is in $parameters? Is it { and } or something else? It appears that tep_output_string will only translate " to " (whatever that does for a URL).
  13. That's news to me. I've seen CE listed for a while now.
  14. But either Frozen or Edge (I think Frozen) was likewise on the official download page until replaced by Phoenix. How has the situation changed?
  15. So did Phoenix finally fix this (replace { } by something else) or is it still broken? It is undesirable to urlencode the { }, as it looks tacky (although it does more or less work). Are there enough saved URLs out there to make preserving the use of { } the least evil choice, even though they're unlikely to work anyway (if not urlencoded)?
×