Marcher Technologies

  • Content count

  • Joined

  • Last visited

About Marcher Technologies

  • Rank
  • Birthday 05/02/1986

IPS Marketplace

  • Resources Contributor Total file submissions: 57

Recent Profile Visitors

112,890 profile views
  1. Why is search setup to fail with full-text stop words?

    Actually not arguing that, just providing information, as that stopwords list changed may not be enough due to that MyISAM limitation.
  2. Why is search setup to fail with full-text stop words?

    It is a default list of words that are so common as to be arguably 'useless' in a search term, as the majority of rows in the database would be likely to be a result. I would encourage you to note that even making this list much smaller, many of the words may still return no result if using MyISAM  due to the limitation listed here:
  3. Handling of multi-value custom profile fields nerfed in 4.X

    Custom Profile Fields Morrigan, not Pages Database Fields. Pages Database Fields have you provide a key, or identifier, with each item, thus this issue doesn't exist there.
  4. Handling of multi-value custom profile fields nerfed in 4.X

    You are correct up til there. He's referring to the fact if a user has provided a selection of value 1 and value 2 while it was configured originally, after updating the field options, it will appear that the user has selected value 1 and value 3 instead in displaying the saved field data. It actually changes the 'value' based on the position in the list.
  5. A way to ban certain guests by ip!

    Is guest caching enabled? If so, the only option *is* what Rhett suggested. Checking that for cached pages in the script would require a query, something the guest cache at this time completely avoids the need for, intentionally, as that is the point of the guest caching = no database connection needed to generate the page.
  6. Better default oEmbed support

    I would encourage you to review the list of providers linked, it accounts for this by providing programmatic access to the embed domain/pattern list via the 'schemes' array for each provider, in essence, it is giving one all the data needed.  
  7. Better default oEmbed support

    The latter is related to the former. Yes, the same list would need be utilized in \IPS\Text\Parser::allowedIFrameBases().
  8. Better default oEmbed support

    While I agree, I could see the complexities of doing so being large enough, that specifically would probably be saner to leave to third-party modifications. While I can add my specific suggestion as well rather easily, I noticed the fact there is no list of what works and doesn't by default is leading to confusion, which this would relieve, as well as utilizing this provider list allowing additions without updates from IPS, or any kind of mod. As a result I think this would be a good move in the software at default.
  9. Better default oEmbed support

    Instead of needing to manually add xyz oEmbed provider, wouldn't it be a lot less grief for all involved if it just pulled from the provider list available here(caching the result for reasonable periods, of course)?
  10. Youtube video allowed in signature!!! YUCK

    Maybe I'm missing the point entirely, but isn't a global block relatively easy with some CSS? [data-role="memberSignature"] .ipsEmbeddedVideo { display: none; }  
  11. IP.Pages

    I've actually been giving this problem a lot of thought already.... there is two sides to the coin, people that want more granular control, and those that want a more global approach instead of needing configure every area individually. Either way, I don't see IPS able to fulfill the needs of both, so I'm going to end up making and releasing something for it, for my own use as well as others. That said, unless someone wants to consign me to make it, customs still will remain a larger priority, so it will take some time to get this finished and on the MP.
  12. CKEditor alternative

    >.< I didn't give up. I refuse to get paid for 1 CKE theme when I am in effect making 7 of them, 1 per browser.... it's not nice to realize that is the case, and it's frankly ridiculous in this day and age of browser standardization. I want to note, I am not upset with IPS on this one in any way shape or form, this is CKE silliness in whole. Just explaining the issue.
  13. CKEditor alternative!/guide/skin_sdk_browser_hacks I would like to point out the problem is much of the default cke themes(including mono) not understanding the C in CSS. Every one of them uses the browser hacks 'feature' to completely redefine the CSS(including colors, often using !important tags) per browser, instead of just tweaks for the browser in question as needed. Custom CKE themes follow this trend by example. This makes it quite the pain to work with, and rewriting it to be sane is a daunting task as well. This wasn't really too much of an issue in 3 because you had customized CKE to the point it didn't use it's themes. Now that it does, it's glaringly obvious the CSS of CKE stock is a pain to work with.
  14. Save IPS Info

    It's actually much worse, for the multi-license user anyway. Instead of one suite you run being compromised, they all are? Oh, and that's not to speak of the marketplace access, including to every mod bought being downloadable, as well as the suite.
  15. Save IPS Info do realize how bad of an idea, security-wise, storing your IPS credentials..... *anywhere* on your site is, right?