Forum Replies Created
-
AuthorPosts
-
September 17, 2015 at 8:13 pm in reply to: The grid.io (AI) system coming online later this year .. worried? #165951coralseaitMember
I think as WP devs we really, really, really need to mature a bit. When REST API is fully baked WP and our ecosystem of mod functions.php or plugins / mini-plugins is going to change. It is a good, possibly great thing, but what it means is that just PHP, CSS3 and HTML5 are not going to be enough.
We WP devs really need to look at node.js / angular / ember / et al and understand that if REST API takes off WP core is just going to be a foundation bedrock and we can interact with that foundation in many, many more ways than theme / child theme with PHP snippets. We need to mature and start understanding more rich UI / Application type fundamentals versus skins so to speak.
coralseaitMemberProbably there's some nasty markup or character encoding in there and it is throwing TinyMCE or the wp filters at post update time.
Go into TinyMCE's text mode and see if you have anything funky in there.
coralseaitMemberNear the bottom of your CSS, before the media queries add something like:
.site-title a { padding: 50px 15px 20px; }
Adjust the first number to around something like 50px; might need to be 51 or 52 or whatever to suit for your needs.
Cheers
coralseaitMembercoralseaitMemberDavinder has it down,
Just as an fyi or something to consider; now's a great time to make sure your new site design has good security and backup. We have no affiliation with the below, but use and love them for all client sites.
1) iThemes security - We use and love this because it integrates well with nginx which is our preferred httpd server on our VPSs.
2) UpdraftPlus - We take nightly backups for all clients to Google Drive and S3; UpdraftPlus allows us to automate this and has allowed us to recover / migrate client sites when they destroy them via content update mistakes or when hosts go out --- it works well in your requested 'click update' scenario
Anyway, as you're under the hood so to speak now's a good time to take security and backup to the next level.
coralseaitMemberHowdy Again,
Victor has given you a good start though. There's a couple things here, given your description of the problem, it is likely one of two things:
1) The varnish cache is still functioning in some way; hence your day expiry and it sounds like siteground do auto expire every 24 hours
or
2) You have cache descriptions on your assets of some sort which are causing browsers to local cache. That's what Victor means when he says expiry headers, eTags, etc - you may be setting info inadvertently that tells browsers not to request new assets. Victor is saying GTMetrix and other tools can help you dig into that.
Also it could be a combination of both.
coralseaitMemberYou might try single quote around the shortcode itself so:
echo do_shortcode('[s2Member-Pro-PayPal-Form level="4" ccaps="" desc="$5.00" ps="paypal" lc="" cc="USD" dg="0" ns="1" custom="fantasyknuckleheads.com" ta="0" tp="0" tt="D" ra="75.00" rp="1" rt="M" rr="1" rrt="" rra="2" accept="paypal,visa,mastercard,amex,discover,maestro,solo" accept_via_paypal="paypal" coupon="" accept_coupons="0" default_country_code="" captcha="0" /]');
But, are these real shortcodes by the plugin or is it doing something like a regular expression check and then replacing things? Sometimes plugins don't actually register real shortcodes, you'd have to check the plugin code to be sure.
coralseaitMemberHello,
I believe that's a transient cache issue, you may need something in functions.php to specifically no-cache or cache flush those on post creation or edit.
We don't use siteground, but reading up it looks like they use varnish for the static / dynamic cache. Combined with the description of your problem it sounds like the caching aging is a day or so. You'll need to ask siteground if you can tune that at all and/or if they recommend a plugin that will flush the varnish cache on post / page creation or edit.
You can also enable the memcached cache and would need something to flush it as well.
Speak with siteground and find out how they can configure the varnish and/or memcache to flush on content changes!
coralseaitMemberHonestly, it is best not to load video on mobile esp on your homepage. Autoplay support is spotty at best, and to be honest with mobile bandwidth quotas, esp in some countries, it isn't so nice to force video on mobile.
You'll also get dinged for homepage payload size by google.
Your best bet is to use a media query to swap in a static image for mobile device in place of the video.
August 25, 2015 at 12:53 am in reply to: White page of death Outreach Pro – front-page.php issue #163395coralseaitMemberDepending on your host / environment there should be an error.log or similar type file in your installation somewhere. Probably in your wp root / html_public folder. If you are on a host that uses cPanel you can dig around and find it.
With debug true, you'll find entries near the bottom of the file corresponding to the problem.
August 24, 2015 at 9:57 pm in reply to: White page of death Outreach Pro – front-page.php issue #163382coralseaitMemberThe problem is here:
//* Add home bottom widgets add_action( 'genesis_before_footer', outreach_home_bottom_widgets', 3 );
At the end of your outreach_home_genesis_meta function, If that is exactly what front-page.php looks like.
You are missing a single quote starting around outreach_home_bottom_widgets',3 );
It should be:
//* Add home bottom widgets add_action( 'genesis_before_footer', 'outreach_home_bottom_widgets', 3 );
coralseaitMemberW3TC is a very powerful, but very misunderstood plugin. You can greatly speed up a site or slow it down depending on what you do with W3TC; most people don't take the time to really understand the intricacies of every setting and what they truly mean. And to gain the most from W3TC you must dive deep into it. It is a good plugin, but difficult for non technical people to understand.
The real answer depends mostly on the specific host and what features they support. Do they offer memcache, apc/opcache, etc and what type of disk infrastructure? These will have the most impact to how well W3TC will function.
We are actually slowly moving away from W3TC; as although we love it, our preferred hosting stack has evolved to nginx with memory base full page cache and HHVM. Soon we'll be using nginx with redis in memory for everything and W3TC will be reserved for those on shared hosting where, because we know the config of W3TC to a tee and can squeeze the most out of limited resources, we'll keep it for those clients that elect shared hosts.
Given a choice we'd rather host on our VPSs with nginx, hhvm / php-fpm fall back and redis (or memcached) leaving caching / performance at the httpd and hhvm/fcgi layer rather than within WordPress. Basically it moves performance optimisation closer to the services than the application and you get far, far more bang for the buck that way.
August 19, 2015 at 10:01 pm in reply to: Display an image instead of a slider on mobile only #162947coralseaitMemberProbably use a media query for an appropriate screen / viewport size.
This shows hiding video for still, but the idea is the same http://demosthenes.info/blog/777/Create-Fullscreen-HTML5-Page-Background-Video
coralseaitMemberHowdy,
Yes you can use the images as is - however, you'll want to question if you want to even do that. You're going to gain a lot by moving to Genesis and HTML5 if you do and one of the most important aspects is responsive design. In that regard, you may wish to question if you even want to force old school layout in your new design.
I understand where you're coming from; but, this is a huge opportunity to re-think your approach. Obviously the images will not scale up and using original size as you have them on the site is just fine, but when you move to a widgetized / responsive design you're going to open doors to more options in your design and won't necessarily be forced to do things based on the size of the existing images and/or text and force text size and image to correlate.
You'll have a chance to really do some analysis and design so maybe take this as a challenge and see what you can come up with.
coralseaitMemberWe use a different method to achieve broad support across many resolutions and devices; waiting for customizer dust to settle a bit before we update it for that.
http://www.coralseait.com/changing-the-genesis-framework-favicon-a-better-way/
coralseaitMembercoralseaitMemberHello,
According to this page, a few lines will setup full width in Genesis with Aesop
http://aesopstoryengine.com/developers/
A few lines of CSS will get you full-width Aesop Story Engine components in Genesis. Just paste this code into a third party WordPress CSS plugin like Simple Custom CSS.
That quoted section has a link off to some CSS : https://gist.github.com/bearded-avenger/f478639cbf0847c48230
coralseaitMemberWe use font awesome and then style how we like; the benefit is simple use and an ever expanding library of icons / glyphs.
Typically we cheat a bit and install https://wordpress.org/plugins/better-font-awesome/ so the site always has FA up to date and then we just use the appropriate markup for icons / glyphs. It is really easy.
Here's a quick examples page from the Font Awesome folks http://fortawesome.github.io/Font-Awesome/examples/
coralseaitMemberAlso a word on why this is important, since you've been compromised once they'll be back and/or sell you to the lists so you'll have an increased target footprint for sometime after this. So once the site is cleaned, you need to up your mitigation and protection strategies because you'll be attacked more frequently.
coralseaitMemberThat could well be a case of BH disabling the site / protecting things etc. You'd need to dump the response headers to see what's really going on as that's a generic message from browser and doesn't indicate much.
Given your experience level (no dig at you, btw), have Sucuri or BH take care of this for you; that ~200 is nothing compared to the time and stress it'll take to do it yourself and more than likely you have to ask BH for help or access anyway.
Once they've done their bit, install iThemes or another plugin and install a backup plugin that takes periodic copies to cloud storage so if you do get taken again you'll have secure backups that don't rely on BH somewhat holding you hostage.
-- Not a commercial here, but for your future reference or anyone reading this later -- Our backup strategy is AT LEAST 14 nightly full copies of all client sites to Amazon S3 AND Google Drive. We don't roll these into our costs but eat it as part of business because we believe so strongly that solid backup is foundation / absolute necessity. By going to cloud storage outside of hosts; we can move sites without the need for the host to step in via DNS updates at most (since we use managed DNS partners moving sites is as fast as the copy takes). If a site is hacked or something goes wrong with a host we can mitigate the damage and move the site within minutes.
-
AuthorPosts