Jump to content


Carl Maltby

  • Posts

  • Joined

  • Last visited

  • Days Won


Carl Maltby last won the day on June 24 2016

Carl Maltby had the most liked content!

About Carl Maltby

  • Birthday 07/18/1976

Recent Profile Visitors

1,761 profile views

Carl Maltby's Achievements

  1. Ticket submitted. Sounds likely, thanks Ryan.
  2. Woke up today to find that one of our admin got hammered with reports about this: I'm guessing that being a cloud-based suite, I don't have access to the files that Chrome console is telling me are having a bad day, and that this should be a support issue? fontawesome-webfont.woff:1 Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID fontawesome-webfont.ttf:1 Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID To be straight, nothing has changed for a few weeks. Literally, out of the blue.
  3. {{$timespan = time() - (60*60*24*30);}} <ul class='feed_image_header feed_image_header_tape{$random_tape}{{if $timespan < $record->mapped('date')}}_new{{endif}} feed_image_header_transform' style='padding: 0px; transform: rotate({$random_angle}deg); -ms-transform: rotate({$random_angle}deg); -webkit-transform: rotate({$random_angle}deg);'> This is how the code works in place, and is more or less as was suggested. What we're doing is to manipulate the CSS classes applied to apply random overlays, add a random tilt to the thumbnail and also add a peeled back "new" label via CSS: It's a nice confluence between the power of what the Invision backbone provides and CSS manipulation of content presentation. Thanks again, @opentype.
  4. Fantastic, thank you general pointers was all I was hoping for but this is right on the mark! I'd come up with a couple of clues and re-warmed my brain, however you've taken it right to the net. ??
  5. Hi all - thanks to the nice stable framework that Invision have created, I've hardly needed to do any code monkeying for months. Understandably, I prefer to create content than fiddle under the hood. Anyway. We decided on our front page feeds that we should mark out which articles are less than one month old and overlay their thumbnails with a "NEW" label. The problem is, I'm so rusty that I literally can't remember where to start....oops.... Our feeds are generated from Block Feeds where a variety of tests produce the layout we need. The only thing I'm tripping up on is the test for conditionally labelling articles as new or not. I'm so rusty that I am only at the point of knowing that this is either "very easy and I'm an idiot for not keeping my chops up" or it isn't, and my rusty chops are being set up against a nice near-vertical challenge. Changing the Feed Configuration to "From the last X days" will not help, as the feed is meant to drag the latest five records, highlight the most recent at top of the list and our intention now is to mark down any less than a month old with an image overlay. Being spoonfed is not what I am expecting, I'm just currently at the stage where I'm hunting for the first clue....! TIA
  6. Our Invision community is ProjectGuitar.com; I have been building guitars and basses for a couple of decades now. Mostly we teach and exchange skills and advice. It's not a hidden talent. Met some absolutely stellar people through our community, seen people go from beginners to industry names and generally find you can never stop learning. My hidden talent is Aspergers. Not sure if that counts? It totally should.
  7. My hidden talent is hidden for a reason. Also, I am not Batman.
  8. The following is an open letter to IPS development management on an issue that affects very old sites, a vital feature whose inclusion would benefit all sites going forward, and the ability for younger client sites to grow with reliance on content integrity vs. internet link rot. I am fully aware that I am far from being the best ambassador to campaign for this powerful and vital feature inclusion, especially from a technical standpoint. I am hoping that the client community will back me up with a can-do attitude where my personal abilities fall short. I am after all better at what I write about than I am the technical aspects of site management and deeper coding. Thanks in advance. ---- IPS, Our site has been a client with Invision for almost 15yrs, and as you can understand we have accrued many many years of content. The nature of our site is a non-profit educational resource, one that visitors and members can rely on to serve years of knowledge accrued by the generous nature of our site's members both past and present. We need to protect that resource, however the tools to do so are not reliable/do not exist and previous attempts to have it figure on the IPS development arc have gained zero traction. Our ability to reliably maintain any weight of content is reliant on a number of things, but has always had a major hole that IPS' development only covers indirectly; that of remote images. As soon as the suite was updated with a remote image proxy cache, we immediately pushed that up to "indefinite" in order that we can best prevent remote images linked within content from going dead. It works, but is a fragile and unreliable feature that is easily lost, with many years of seldom-visited content still not cached that may go dead in the meantime. We specifically upgraded our hosting tier to purchase additional account disk space month-on-month. We are paying to preserve content, as this is crucial to maintaining well over a decade of valuable content going forward. With the recent changes in Photobucket's remote image linking policy, remote image link rot has accelerated enormously becoming the hot issue for many site owners. We do not expect that this will improve, if anything the opposite. We need a defensible mechanism to preserve site content in line with the otherwise professional-level that we have come to expect of the IPS suite. My proposal suits both the objectives of clients and IPS; the growth of sites is helped considerably by our ability to maintain older content with integrity. Whilst some cloud clients such as ourselves may pay for a higher tier than required just to accommodate a proxy cache, growing sites will do so as their membership increases as any reliably-curated site with quality content tends to do. To put it another way; we are in the content business, so we need the tools to protect that content. By giving us the ability to do that, we become better-paying customers. That IPS have not specifically added this already is somewhat obscure and difficult to understand. We are all losing our older content and the tools to reinforce it are not being added. Older sites are uncontrollably decaying, and equally, younger sites cannot fully mature as link rot snaps at their heels. This must change. The following identified mechanisms would be infinitely-valuable for clients at levels: The ability to convert remote linked images into discrete embeds Post-level, thread-level or forum-level methods of pulling a proxy-cached image into posts as specifically-attached media. Proxy cache versioning Proxied images with several versions that can be selectively pushed using the previous mechanism. This prevents "poisoned" cached images such as a remote site's default placeholder image from taking precedence over the intended image. Whilst several other ideas exist, these basic tools would represent a huge step forward for content-curators and sites that need to preserve valuable content going forward. IPS - I hope that you can engage in meaningful discussion here in order to make this happen. Currently there appears to be zero interest in making an essentially vital tool even possible for clients.
  9. Thanks Rhett. Ever since remote image caching was introduced, the idea of permanently caching remote images has been bubbling under the surface and I think that it would make sense to introduce some method of automatically or electively shifting remote images from the cache into discrete embeds. Unfortunately, I do not have the experience to do this myself for our own site as my skill set lays more in content generation than coding work, and I am sure that this lays more in the code we can't easily work on when it comes to cloud-based sites. Obviously there are implications of intellectual property rights when moving images from being merely remotely referenced to being discretely "site-side" which I presume will be best dealt with as part of a member's signup and site terms of usage. Does this figure into the roadmap at all, and would it in fact be useful to push into the development suggestions? I'm not really hands-on enough to know whether this is something that better lays as third-party development or within that of the suite itself. This is a strong and frustrating concern, especially since the remote image cache settings have been themselves reset during suite updates (4.2.x being the most recent) and support staff maintenance, resulting in our otherwise extensive (and important) cache of remote images having been dumped for re-caching when most don't necessarily exist any more. The recent changes to Photobucket remote image hosting has only made this a larger priority. As a site that is hosting almost 15yrs of educational tutorials and how-to's, a reliable method of fending off image link rot is worth its weight in gold. We've already lost way too much to Internet entropy and need to ensure that our library of forum posts can be preserved! Apologies for the large post.
  10. Hi guys - hopefully this is a quick answer, however I've not found it in search simply because so many people complain about statistics in general....I don't want to weigh in on that.... So anyway. I have a block which I am using to push code onto a page encouraging registration. "Register now, you will be member X" where X is member {number="$stats['member_count']"} plus one. The thing is, that only seems to work in a block set up for member statistics, which this one is not. Can that value be pulled independently?
  11. I am experiencing this same issue also; I uploaded images to Pages > Page Management > Media, which have tag references such as:' {media="base-images/tape.png"} In one of my Pages > Page Management > Templates I have a CSS file which references several of these: .feed_image_header_tape1 a:before { background: url({media="base-images/tape1.png"}) no-repeat; } .feed_image_header_tape2 a:before { background: url({media="base-images/tape2.png"}) no-repeat; } .feed_image_header_tape3 a:before { background: url({media="base-images/tape3.png"}) no-repeat; } .feed_image_header_tape4 a:before { background: url({media="base-images/tape4.png"}) no-repeat; } .feed_image_header_tape5 a:before { background: url({media="base-images/tape5.png"}) no-repeat; } The page's HTML renders out as: .GOTM_image_header_tape a:before { position: absolute; z-index: 2; content: " "; top: -25px; left: 50%; width: 242px; height: 54px; margin-left: -121px; background: url({{media="base-images/tape.png"}}) no-repeat; }
  12. Hi all. I've become highly averse to using the template manager of late simply because of its awful state of usability. Being a fundamental way of controlling how site content is manipulated and indexed for users, this undermines the package at a very deep level. Do let me know if I am somehow over-reacting or missing something here....or chime in with your own comments.... I'll discuss my primary bugbear, which is the database templates....they are after all the bread and butter of a Pages-based site. groups of templates are easily created from default, but immensely tedious to delete one-by-one groups cannot be deleted en masse deleting one template from a group re-orders the group listing, easily causing template deletion from the wrong group there is no method of arranging templates into any sort of order beyond what the ACP arbitarily decides from minute to minute templates cannot be moved between groups or copied Obviously bringing problems to the table is nowhere near as useful as bringing solutions, I propose the following ideas: A "recycle bin" for templates and groups this could be implemented by simply "greying/redding-out" the group or templates in the tabbed listing A drag n' drop tree management system for arranging templates and groups into sense order Second-level nesting of templates I tend to arrange my templates by-database, for example "Articles" and "Tutorials". The current system requires that I either have an overly large first-level listing of "Article Form", "Article Category", "Article Display", etc. as groups or a single group containing all of these individual templates, including occurrences of identical names ("index"). A second-level listing would allow a group "Articles" and a logical group of "Category", "Display", etc. Common templates Reducing redundancy and inconsistency is a key job. For example, a simple templated method of displaying an element common to various database - such as a Category row - is replicated amongst every occurrence of Category templates. The option of setting a template (such as "Articles > categoryRow") as a clone of a common template (such as "common > categoryRow") would hugely reduce unnecessary template proliferation. Deleting a template with dependencies would of course need to be captured. In fairness, this is the tip of a very large and frustrating iceberg. Is everybody else finding the template manager unintuitive and slow to use? I'd rather be generating content instead of chasing around the template manager!
  13. Correct, that's what we surmised. Caching seems to be working at the moment for other hosts.
  14. We are also experiencing issues. These were shared from Dropbox and seem to work for the poster.... http://www.projectguitar.com/forums/topic/48305-knightro-guitars-2015/?do=findComment&comment=547579
  • 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