Forum Replies Created
-
Posts
-
We take a different approach, as site security and backup and availability are extremely important to us.
1) Never rely on the host for backups
2) Use use UpdraftPlus and take nightly (at least 14) backups to S3 and Google Drive of all clients
3) We use iThemes (mainly because it integrates with nginx, our preferred httpd server).
We offer value added services where we do all maint, etc because we feel keeping sites up to date and secure is very important. Therefore, at least 14 nightly backups come with all sites and if you use managed services with us all updates, seo, etc.
Yeah, we understand, it is tough when starting out.
Thanks for the heads up on home page. The VPS company is shuffling things around in the data centre due to a fibre outage and we've just decided to wait it out versus failing over to backups!
Hello Again,
Probably in the thousands range; typically it is a very full featured / full app style scope. Apologies, I know that's probably not what you'd like to hear.
All of the sites we've done this for are behind customer portal logins, I can ask clients if they're willing to have you sign in and look though? Generally they're really closed about them because there's a lot of competition in the area and they love what we've done and don't want it replicated. Many have come from conversion of existing custom apps or moving off hosted solutions and find what we've written to perfectly fit their needs so they don't want it spreading. Sorry we don't have better news there. We've thought about writing our own plugin for it, but the selling point would be too high for the typical market to adsorb because they are really well featured systems.
I think the best bet is to look at the hosted app options for proofing; or if you'd like a more expanded discussion on features and scope to nail down a more targeted quote happy to speak to you about it. Most of the clients are large agencies handling large portfolios of photographers and clients so their needs are very detailed.
You'll find the trouble with the hosted apps; they start to balloon in costs as they take a cut per image / proof; but it is a good place to start and when your qty / volume grow you can look at custom apps. Envira may work as well, but it sounds like your options selection settings are not enough with the plugin.
This is a really tough nut to crack, because most Photogs need the expanded features but the budgets are tight (we understand) and so the bigger agencies are the ones that can absorb it with their large client and volumes.
We've ended up writing custom functionality for proofing for most photography clients who desire it. Along for the ride always comes custom gallery stuff, as they want (and rightly so) the galleries and proofing integrated.
Each time we review proofing plugins and options we find them lacking in a few key areas that don't align to our Photography clients' goals and they have us write them something. These can then be integrated with eCommerce, but the majority of our clients are not selling prints, they are selling entire wedding packages, real estate and aerial drone / aerial photography where entire shoots are proofed, retouched, etc and don't really lend to eCommerce or commodity print selling of the product (i.e. there's often heavy retouching and post processing so each photo is unique and doesn't lend to a print style business).
Anyway, what we've written does align mostly with what you ask for, as the style of photog business mentioned above uses a menu / al carte style ordering concept with options for the retouching and proofing; often to each image level. It can certainly be done and done well. Note, it has been a few months since we reviewed plugins so something better may be out there now.
Another options is to use a hosted service for this instead of a WP site, many of our smaller / more simple photographer clients do this instead in the print as good style business, as the hosted proofing apps do that well.
Just lending our experience.
Can't look right now, but if it is problem only on smaller view ports it'll be in the media queries part of the stylesheet.
Hello,
Before you head down that route, step back and ask yourself if you really need a native App (Native as in written for iOS or Android, not just a web app). Your support footprint is going to explode and multi device support is a pain. If you don't have compelling reasons to use a native app the time is better spent on good responsive design and content.
The permissions mask that you have to change to indicated a user, group or other ownership problem, and this may be on the parent directory as well. It is probably group membership issue.
I think Porter is on the correct track with file and directory ownership. Typically in hosting panels you won't see ownership or expanded ACL info; just file masks (644, 755, etc).
Basically, the directories and files need to be owned by whomever the httpd that serves WP. The host should know, and you may have to ask them to chown -R to the webserver owner (or whatever they recommend).
How did you migrate this onto to the host? I've seen this a few times with some plugins that fail with some wp population and fail back to less graceful methods, sometimes leaving ownership not set properly.
That'll be it, you can tune the W3TC minification to exclude whatever CSS / script it is puking on so you can get most of the benefits of minification.
However, generally it'll come back and bite you some time later when the child or framework update. Best just to leave minification off.
You can also try https://wordpress.org/plugins/autoptimize/ plugin which tends to minify more intelligently (use W3TC for everything else).
I recommend when using FA for things like lists / menus to use fa-fw within your classing. This forces fixed width and aligns things without your needing special CSS (most of the time). As this is probably set in css custom style of your menu item you'll do as Victor said as it is a little bit different when in menu items - but this is a tip for general use of FA in sites; when doing lists, menus, etc use fa-fw as it'll make your life so much easier.
for example:
<i class="fa fa-fw fa-home">For more info, see https://fortawesome.github.io/Font-Awesome/examples/ Fixed Width Icons
Is the site the same property / branding for main site and blog? If so, there's no need for two separate installations unless you have some functionality concerns.
That'll just add more admin burden. Now, if there's some security, branding or functionality reason by all means use two installs.
Whilst true this is a community support, we're the ones who will be building on the Framework and REST, so good to start discussions and exploration of what we can do with the two combined!
Hello,
Can you describe a bit more detail, what OS and Browser(s); it looks ok in Chrome and IE in windows (the only ones I have available right now).
An easy way for non tech / programmer folks to get around the order issue is to change to post date, and force the post date date of the slide posts.
So the first slide, make it the most recent post date / time. Second slide post, earlier than the first (say an hour), third earlier than the second, etc.
Not sure on Safari, not on a computer I can test that now.
Sorry to be a bit of a pain, but this could be coming from so many plugins / places.
Do you have access to error logs? If so turn debug mode on and we'll be able to discover more info of where this comes from.
You've got that a bit in reverse; what's in style.css is the site's CSS. Inline style is when embed style / CSS into the content itself usually via the text editor in WP or within widgets, etc. This overrides the site's style sheet.
Generally, we devs / designers frown on inline styles and prefer classes / selectors within the style.css (or other style sheets, you can have more than one if you desire).
The (simplified) reason for this is that inline styles force you to make any changes within ALL the content where you've used inline styles vs. in the one or two places of a style sheet you reference. There are other reasons as well, but keeping it simple per your comments on just learning this.
As a summary:
Try not to inline your styles / CSS - use the style sheet with classes or id selectors if you must.
Plenty do; however, as victor said Shortcodes are handled by WordPress itself not necessarily the framework.
And WordPress is right in the middle of changing how shortcodes function across the board; so anything you adopt right now may well change. You've asked right in the middle of a major sea change in the WordPress Shortcodes API
So Victor and I are saying to carefully read up and follow on any perspective shortcode plugin; esp as the Core Team has warned they will be doing even more changes to the short code API; this last time caused considerable consternation.
If you'd like to see where the team is indicating they are heading with shortcode api see:
https://make.wordpress.org/core/2015/09/29/shortcode-roadmap-draft-two/
The main question is do you mean managed hosting or self managed?
We run a VERY performant stack on our self managed VPSs - however, if you are not up to speed on LEMP it's not a good idea to replicate something like what we do and instead seek a managed provider. In that space we can't help much with recommendations, but if you can self manage a VPS happy to offer suggestions.
As Victor mentions recent changes have occurred; but not only that, the WP Core team has said that Shortcodes will be changing even more so probably best to stay really close / up-to-date with what Core will be doing with Shortcodes.
