Jump to content

Community

Myr

+Clients
  • Content Count

    718
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Myr reacted to bfarber in PageSpeed Insights -Going to Improve?   
    On a completely fresh install of beta 5a we saw yesterday a score of 91/100 with the Pagespeed tool for Desktop, and 83/100.  Note that this can depend upon your server configuration (for instance, whether or not you have gzip enabled for resources).
     
    We will not be addressing the "Eliminate render-blocking JavaScript and CSS in above-the-fold content" items that the pagespeed tools refers to at this time, because it is extremely (near impossible) to handle this properly in dynamically generated software that users subsequently adjust and modify.  For instance, the tool suggests putting all CSS necessary to show the "above the fold" content inline into the page, and then using javascript at the bottom of the page to import the rest of the CSS.  Firstly, the amount of CSS that constitutes what is necessary "above the fold" would be astronomical, and you would take a hit elsewhere with respect to reducing the page size and caching.  Secondly, it would be very error prone once you start factoring in addons, plugins, third party skins and template edits.  Finally, because of the amount of CSS necessary, it would likely reduce your score in other areas.
     
    That said, with a fresh install showing a score of 91/100, we feel that is a pretty respectable score.
     
  2. Like
    Myr got a reaction from azcazc in PageSpeed Insights -Going to Improve?   
    Cool.
    I know the tool isn't flawless, but it is what Google offers and we all must dance to Google's tune or pay the price in the rankings.
  3. Like
    Myr got a reaction from SJ77 in PageSpeed Insights -Going to Improve?   
    Cool.
    I know the tool isn't flawless, but it is what Google offers and we all must dance to Google's tune or pay the price in the rankings.
  4. Like
    Myr got a reaction from BariatricPal in PageSpeed Insights -Going to Improve?   
    Cool.
    I know the tool isn't flawless, but it is what Google offers and we all must dance to Google's tune or pay the price in the rankings.
  5. Like
    Myr got a reaction from NewRockRabbit in IP.Downloads and IP.Commerce Integration   
    From what I could tell from the brief appearance on the test server, we're still stuck with single-sale downloads only.  We're selling eBooks on our site and it is critical for us that customers are allowed to buy more than one download at a time. 
    Can we get an answer on this?  I need to know whether we need to start working on replacing our eBook sales solution...
  6. Like
    Myr got a reaction from opentype in IP.Downloads and IP.Commerce Integration   
    From what I could tell from the brief appearance on the test server, we're still stuck with single-sale downloads only.  We're selling eBooks on our site and it is critical for us that customers are allowed to buy more than one download at a time. 
    Can we get an answer on this?  I need to know whether we need to start working on replacing our eBook sales solution...
  7. Like
    Myr reacted to Rimi in When is IPB 4.0 ?   
    And nobody really disagrees with that. Problem is some of us would like to start new projects and anyone who's dedicated will at the very least build a custom skin for their site and perhaps do some hook or app customizations. But IPS is reworking 4 from scratch meaning that with 4 people will have to remake their skins, hooks, and apps from scratch. That's really why people care so much about getting more information about a release date. If there is an internal projection (yes they have internal deadlines) of mid to late spring then people would benefit from knowing because they can hold off on their project. If we're talking about summer then people might be more inclined to launch a project off now and be moderately ok with redoing all customization work once 4 is out. Having a ball park estimate of a release date does affect everyone. But IPS won't give it to us because they already guessed 2013 and missed by a mile and people's reaction was to basically throw a fit.

    This isn't about having a stable product, or having lots of new features. It's a simple request for information so that customers can plan what to do with the product. Nobody, absolutely nobody, wants to commit to 3.4 with the idle thought that IPS 4 will be released by the time their project launches.
  8. Like
    Myr got a reaction from OGN in When is IPB 4.0 ?   
    It has been quite awhile since the last blog post.
  9. Like
    Myr got a reaction from PrettyPixels in When is IPB 4.0 ?   
    It has been quite awhile since the last blog post.
  10. Like
    Myr got a reaction from djpretzel in When is IPB 4.0 ?   
    It has been quite awhile since the last blog post.
  11. Like
    Myr reacted to GreenLinks in When is IPB 4.0 ?   
    Key blog entries we are awaiting :

    Search Relevancy
    Searcn Engine improvements / additional search engine supports
    Ip.Content management
    Ip.Content content creation
    Notifications
    Gallery Improvements
    Content Expiry improvements for better nginx/varnish support
    And surely
    Frontend UI
  12. Like
    Myr reacted to OGN in When is IPB 4.0 ?   
    been a while since we got a blog entry :P
  13. Like
    Myr reacted to Charles in When is IPB 4.0 ?   
    I think everyone will enjoy the polish that is 4.0. Here's a proper teaser. (Please do not ask for details on this feature beyond what I post here as I won't answer :smile: ... details will come in blog entries.)

    This is the popup that comes up with you click to follow a content item. Here I clicked to follow a file in the IP.Downloads 4.0 section.



    Compare that to the existing follow dialog and you will see just how much more user friendly it is.

    It's brighter, bolder, and easier to read. The options are clear and not hidden behind drop down menus. The toggle to allow others to see that you followed is also very clear and bold The title of what you are about to follow is shown Notice how the first option is disabled because I have not set up my user notification options. The system notices this and gives me an explanation why it won't work and a link to correct it. In doing so it solves the problem of people following something and not understanding why they get no notification and, more importantly, guides the user to the notification options so they can see all the great tools they have to keep up to date.

    So just a quick example of the polish and thought being put into 4.0 for you :smile:
  14. Like
    Myr reacted to Matt in When is IPB 4.0 ?   
    It's very different. You can tell that it has IP.Board DNA, but it's a modernisation of our look and branding. I think you'll like it, though.
  15. Like
    Myr reacted to bfarber in Using Font Icons   
    We are using font icons by default in 4.0.
  16. Like
    Myr reacted to Mark in Will IP Social Suite (4.0) follow proper HTML5 web standards and be valid?   
    From our coding standards:

  17. Like
    Myr reacted to Matt in Social share has a huge gaping hole - pm this link   
    I phoned your Aunt, and she said she knew exactly what it meant. I also stood in Piccadilly circus and asked passers by. Not many stopped to give me an answer, but I did collect £1.78 in loose change tossed at my feet, so not a complete waste of time.
  18. Like
    Myr reacted to Matt in Editor Feedback   
    Thanks all for the feedback so far. There's lots to think about.

    Can I reframe the question a little, though? Taking on board what you've read in this topic from the 26 customers who've replied but not forgetting the thousands of other customers and the potentially millions of end users, what would you do if you had 2 weeks to focus on the editor? Keeping in mind backwards compatibility and existing functionality?

    I'll run through some of the points raised so far:

    I'm not against adding parsing 'modules' such as mark-down but you do of course exponentially increase the amount of code and maintenance needed. Our CKEditor implementation is directly tied to BBCode downstream so it's not as simple as just adding a new parsing module within CKEditor. You'd also need supporting PHP to post process that.

    We don't directly store *all* BBCode as HTML. Previously we stored the posts as BBCode and then parsed it on view (and then cached it). The issue with this is that we ran into trouble trying to parse it on view and parse it back for CKEditor (as what CKEditor needs is slightly different from what a normal post view needs). This introduced quirks and bugs. Worse, when you toggled HTML to BBCode mode it fired off an Ajax process which introduced bugs and quirks in two separate layers (JS > PHP (to convert from HTML to BBCode) > JS). This was especially hard for customers with a need for extended characters (accented characters such as those in the Polish and Russian languages). I got a steady stream of tickets and bug reports from these customers who found issues such as characters going missing or incorrectly becoming encoded. By the time the last release of the 3.3 series was made there was a kludge of methods and functions that converted characters over and back again through the various stages of BBCode parsing. One the post was saved, PHP code made an attempt to convert that HTML to simpler BBCode and store it in the database.

    It was clear this was not a method with a healthy future as the code had become horrifically complex and almost impossible to fix with a simple one line change causing ripples throughout the entire parsing code-base that took forever to track down and resolve. Trying to fix a bug was like taking the last few turns in a game of Jenga.

    My approach for 3.4 was quite simple: remove BBCode from the IPB PHP code and have it as a plug in for CKEditor. This is exactly what CKEditor is designed to do; replace the source mode with your own function. This means that IP.Board only ever has to deal with HTML from CKEditor because even when you're using the source editor, it's converted back to HTML before its saved. This greatly simplifies what IP.Board has to do and removes the Ajax step when hitting Source mode thus removing a lot of code that was a source of the character set issues we routinely faced.

    This means that we don't have to store posts as BBCode anymore. We store them as *mostly* parsed HTML cleaned from CKEditor. Custom BBCode, media tags and emoticons, etc are *not* saved as parsed and still parsed on viewing the post (and then cached). This approach has allowed us to remove thousands of lines of code and all the potential bugs that it could generate.

    Now, this change has been painful and I am sorry about that and I agree that we should have focused more on testing. I felt confident the editor was stable after testing it on our company forums for well over three months and having it in QA and beta testing for about a month but unfortunately we didn't thoroughly test all permutations such as HTML mode, etc. Furthermore, backwards compatibility was initially troublesome as the parser had to process posts made with previous versions of IP.Board that were all in BBCode and convert them on the fly. Matching up legacy parsing to the new parsing engine cause some teething issues which have now largely been resolved.

    I know it seems that we've taken a backwards step in terms of stability but I am very confident that once the kinks are ironed out, we'll be in a much better position to move forwards. Already the code is much simpler to bug fix allowing me to race through tickets and bug reports much faster. The fixes don't impact other areas generally either now as the code is better written and each component of that code works without being intricately tied to another piece of code (tight coupling).

    The JS engine to convert HTML to BBCode is brand new and as such has to face lots of untested mark-up. It's quite a feat to take a HTML document, explode it into an array of nodes and then convert them to BBCode cleanly and then back again. I'm confident we're on top of these issues too.

    Things like reverting back to adding in text QUOTE tags when hitting 'quote' I'm less keen to do (not least of all because it will mean rewriting parts of the current parsing engine) so I'd like to hear what you dislike about having quote boxes appear in the editor as styled elements and now we can make that better.

    Similarly, CODE is a challenge because we now use <pre> tags so you don't have to maintain <br /> to n conversion and back again. The code box that is added when you click the button is a PRE wrapper that CKEditor understands maintains its own newlines. If you manually type in the CODE tags it doesn't have this knowledge so PHP on the back-end (and the javascript engine to convert to BBCode) needs to make a guess as to where the newlines should be which leads to bugs that you never truly fix but rather push around.

    Generally speaking, it's hard for IP.Board to understand what you want when you start manually typing BBCode tags while in the RTE mode. You have to take the HTML CKeditor gives you and parse it twice (once to clean that HTML and again to parse BBCode) which will cause issues and bugs (again, that are just pushed around and never truly fixed).

    I hope you understand this post was meant to educate on the challenges and not a flat our rebuttal on the feedback gathered so far.
  19. Like
    Myr got a reaction from wmarcy in All IPB forums breaching EU law   
    Well, if any fines come my way from the EU, then I will do the American thing and tell them exactly where they can stick it, as loudly and obnoxiously as I can. :)
  20. Like
    Myr got a reaction from TaffyCaffy in All IPB forums breaching EU law   
    Well, if any fines come my way from the EU, then I will do the American thing and tell them exactly where they can stick it, as loudly and obnoxiously as I can. :)
  21. Like
    Myr got a reaction from Nick² in Dropped the ball on Mobile and Apps   
    I know I'm in the minority here, but how about a Windows Phone app...
  22. Like
    Myr reacted to bfarber in Dropped the ball on Mobile and Apps   
    We will be releasing an "actual" app, yes (you will download it from the app marketplace, not from us). We had one in the past and decided to overhaul it from the ground up taking a different approach, and that app is currently in heavy development.
  23. Like
    Myr reacted to ᴡᴅツ in I like where IPS has taken IPB   
    Congratulations on a job well done. I really like the improvements you guys are making within the internet communications industry. IPB is really looking like the best forum out there, especially with such a nice suite available.
  24. Like
    Myr reacted to Clickfinity in 3.2 Wish list ...   
    I appreciate Matt and the team have their own plans and are probably well on their way with 3.2, but here's what I'd like to see for CycleChat:


    View new content - Show what is actually new (unread) content; show topics only (as opposed to multiple posts from the same topic). Hover preview (really liking the new version) - To work on forum view, all search results, and personal conversations - with ACP options for trigger time, and post-hover fade time. Thread marking - to mark up to where I have actually read in a thread, rather than marking the whole thing as read. (Matt has said this is on the list - yippee! :thumbsup: ) Lighter CSS - There's tons of the stuff ... can it be made lighter by making more "global" style attributes (with the option of adding custom code if needed)? Better editor - I've lost count of the number of "issues" people have had with the post editor. Hopefully some improvements for 3.2? Emoticons as a pop-up perhaps? Simple alerts, likes, and trophies - Not strictly an "everyman" feature set, but after playing with xF this is something I think would greatly improve member-engagement at my site. Simple out-of-the-box Article system - IP.Content is great, but confuses the hell out of me. I just want a simple, categorised, article system where I select from a pre-built template, apply my site "style" as a wrapper, and then start adding articles. Expiring notifications - Once I've read a message, remove the notification about it. I'm sure I can think of others, but that's not a bad start for now.

    Cheers,
    Shaun :D

  25. Like
    Myr reacted to Adriano Faria in [3.1.4 or 3.2.0] Add a link to hook settings in 'Manage Hooks'   
    This is something really boring and extremely repetitive. Every time we install a hook, we have to navigate to Edit Settings, click thousands times until you get the settings for the specific hook. It gets worst if you have several hooks installed.

    One simple thing would be to add HOOK SETTINGS in Manage Hooks, right here:



    The idea is to centralize everything in one area, save time!

    Please consider this! :thumbsup:
×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy