Forum Replies Created
-
AuthorPosts
-
Bill MurrayMember
This is accomplished by using a plugin such as WP Touch. Mobile responsive does not normally provide for this functionality, because mobile responsive involves serving content based on the browser's width, not the device. Approaches that use "switch to desktop view " are generally part of server side processing where what's served is based on the device requesting it.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberIf you don't have a live site, you're better off to start with the beta because you can work with HTML5 and the current hooks.
If you do have a live site and it's not on Genesis, you can still start with the beta and focus your conversion work on building an HTML5 site using the latest features. You should just wait to launch a live site until Genesis 2.0 is out of beta. That said, there are several high-traffic sites that are running the beta now. Nothing will blow up if you use the beta, and if you're comfortable with solving problems, you could launch while 2.0 is still in beta.
The beta will change between now and final release, but your time working it will not be wasted. Changes from here on out will be subtle.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberIt's not likely a problem with the custom menu widget.
Have you checked your user role on the site? Is it administrator?
What gallery plugin were you using?
Who is your host?
Another possible problem is that the index on your postmeta table is damaged or corrupt. You can repair the table using PHPMyAdmin (your host should be able to help you with that if you don't know how to do it). If your postmeta table is non-existent, damaged, or corrupt, you'll see the pending status when you attempt to add new menu items.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberYou're never going to get an accurate answer to your question. SP will release Genesis 2.0 when it's ready, after WP 3.6 is released. WP 3.6 is getting close, but there's no firm date. When it's done, it's done.
The theme you mentioned will be released after Genesis 2.0 and after WP 3.6, but there's no telling how much later. If you want to get started using Genesis 2.0, you can set up the beta along with the sample child theme and be that much further along for when things are released.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberAccording to others, Travis Smith (the developer of the Genesis Latest Tweets Widget plugin) was out of town and just got back yesterday. Yesterday, he did tweet that an update would be out before the end of the day, but that time has passed. Twitter made a number of changes in the new version of the API, the biggest of which is that version 1.1 now requires authentication. As a result, it's more than a few minutes of work for Travis to update the plugin. For example, there's a URL in the plugin that was used to capture tweets, and that URL changed, but the changes Travis needs to make are more extensive than just updating that URL. I'm sure it will come relatively soon, but I think it will end up being longer than some of the more optimistic projections.
If you want to restore a Twitter feed to your site, you can use Twitter's script directly or you can explore the Latest Tweets plugin. That plugin works with the new API and includes the OAuth authorization method for solving the authorization issue. If Travis ends up using OAuth authorization (a very reasonable method), the setup you go through to create credentials at Twitter will put you a step ahead of those who find out about this when he releases his update.
Of course, you can just remove the widget until the plugin is updated. The internet won't break if a few sites drop their Twitter feeds.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberMy initial reaction is that this is either a) a caching issue or b) a problem with your host.
On a quick look, it doesn't appear that you are using any caching plugins, but are you using any object caches (eg, APC or memcached)? Problems with object caches can produce the problems you are describing. If you are using any caching, disable it and see what happens. Check with your host and see if they have installed any caching that you might not be aware of.
Next, keep in mind that WP stores its data in a database. If you can access the DB directly (such as through PHPMyAdmin) and you know your way around the WP DB structure, you could see if the data that is missing on the frontend of your site is still present in the DB. If it has gone missing from the DB, your host might be having MySQL problems and not telling you, or your host might be restoring old copies of the DB without telling you. Another possibility is that your host is having DB problems but is unaware of them because they might be affecting a limited number of customers.
Your best bet is to have a conversation with your host. In a normal hosting situation, WP won't mysteriously drop your data in the way you have described.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberIf you load the script in the head, it will track stats for every page, provided that: a) the visitor has javascript enabled and b) the visitor is on the site long enough for the script to load.
That (b) is important in that the Google javascript is asynchronous - it won't block loading the page. If your page otherwise is "heavy" and Google's servers are a little slow at that moment, a visitor may leave your site before the tracking script finishes loading, so that visitor won't be tracked.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberThey were retired, which means you can no longer purchase the themes, but support is available for existing sites that use the them.
FYI, we do managed WP hosting, and both of those themes are available for new sites, so if you're committed to 1 of those themes, there are ways to still use one on a new site.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMember@rfmeier - Thanks for the followup, but I wasn't referring to cPanel. For example, if you get a VPS with HG, you can get cPanel, WHM, and Parallels. It makes managing your VPS easy. That has nothing to do with optimizing it. Out of the box, a level 4 or 5 HG VPS won't deliver results that are much different from HG shared hosting because out of the box, the VPS is not optimized. It is there for YOU to optimize - and secure.
You have to be a server admin - that is, you have to understand how to optimize the OS (some flavor of Linux, usually), the web server OS (usually Apache, and by default on HG VPS, but this is a bad choice), and handle security, logging, etc. That is a big scope of work that most WP people - and even most tech-savvy programmers - never touch. If you're thinking that you can call/chat with HG support and they can "walk you" through doing that, think again. The support people at HG that are your first line of defense don't know the information themselves, because they are not server admins and they have no knowledge on how to optimize a server for an application such as WP.
And imagine you go the VPS route: at the end of the day you have 1 webserver and the responsibility to manage it. If your webserver dies, so does your site. If you update a plugin or WP, you have to put your site in maintenance mode and are off-line, even if for a short time. In our managed WP world, we have multiple web servers AND multiple DB servers. If 1 were to go down, it would not bring down any site. We're able to do updates without a site ever going into maintenance mode. And those big performance/reliability benefits come with something that is tuned for WP, the application a WP site plans to run.
In the not so distant past, VPS's were way over sold as a panacea for performance problems. They're far from that. When a customer at HG would complain about performance problems, the default answer (from HG and many in the tech community) was "upgrade to a VPS." Even for those that have the skills and desire to be a server admin, a single VPS is not a great route. I think if your budget can't afford a load-balanced, multi-server solution (which I don't think HG offers anyway), then managed WP hosting is a clearly better choice. For example, if you look at managed WP hosts (us, wpengine, websynthesis), I don't think any of us are running Apache (I know we aren't). In order to want to get into the VPS world, you have to know why Apache is not the best choice and how to set up the best choice - and that's something that is beyond the skill and interest of most people wanting to host a WP site.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMember1) I wasn't suggesting there is a conflict running CloudFlare and CloudFront together. Instead, I was advising that's the wrong way to go about optimizing. When you optimize, you add 1 improvement, measure the results, and only when satisfied whether to drop or keep that improvement and with a new set of stable benchmarks in hand do you add another improvement. Otherwise, it's impossible to know what hurts or helps.
2) To get the page weight down, you have to remove stuff.
3) On the stats I posted, I agree with you they are obvious, but my intent in posting them was not to belabor the point. I was trying to point out how bad they are. I've been doing this a long time. Your stats are some of the worst I've ever seen.
4) You say you want to verify it is a server side problem but you also say you aren't a tech. I don't mean to be impolite, but when you aren't a tech, you have to lean on the opinion of others with knowledge. Your site has 2 problems, the page weight and server issues. The server issues are the bigger problem. Your site essentially as you have it (without CloudFlare, CloudFront, or any caching plugins) would load much, much faster on our servers. If I had to guess, I would say first visit loads would come in around 2 seconds (which I'd still consider less than ideal), and repeat visits would come in at about 7/10's of a second. I could write pages and pages on WHY that is the case, but I'll give you the condensed version here: a) your current web server is not running the most optimal OS; b) that unoptimal OS is not configured for your needs (it's configured for easy maintenance for HG); c) that unoptimal OS is running on a server where others can consume the bandwidth (however, HG is pretty good at monitoring this, so it's not the big culprit here); d) the server is not load-balanced among several servers (since you are on just 1 webserver), so when your server memory runs out, visitors must wait for the server to become available; e) WP gets data from a database, and your DB connections are slow, from a single server running a less than optimal storage method, and are not aggressively optimized; f) if you are using any caching or security plugins, they are running in PHP, and PHP is much too late to be doing that; for example, we cache aggressively, but we cache at the OS level, so cached requests never reach PHP; in other words, via a cache we can serve your site without a DB, without WP ever firing up, and without PHP ever executing a line of code - things you can't come close to. As I said, that is a condensed version of why your site is slower on a shared host.
5) While I agree with much of what @rfmeier has posted, I don't agree that a VPS is a good route for you, or for most people for that matter. If you are considering a VPS, ask yourself 1 question: are you currently a server admin or have server admin skills/knowledge or want to learn it via trial by fire? If not, skip VPS. VPS's require server admin skills, period. You will either waste more time trying to become a server admin or have a VPS that costs more than your shared server but performs about the same.
6) Thanks for the heads up on the landing page. I'll check it out. The landing page is there to reduce new business, because we are busy, which is common in the WP world right now. When time permits we'll take it down. If you have specific questions, I'll try to answer them. I only offered info on us as a frame of reference. I'm always a little amused when people talk about not affording managed WP hosting. Using our numbers, @ $20/mo or $240/year (and we have cheaper plans), you should not waste any time fixing your site speed issues. Your hourly rate is likely above the annual cost of fixing your problem. Mind you, that is not poking at you to "host with us" - it is poking at you to switch to a managed WP host, pronto.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMember@pensacoladisabilitylawyer - My sense is you have a problem (slow page loads) and are throwing too many solutions at the problem (eg, CloudFlare and CloudFront). Your site has too much page weight (at 1.76 Mb), largely due to too many images. Beyond the page weight, as others have already said in this thread, the variation in the page loads are due to the design of your shared host.
In 10 tests I did simulating a 5 Mb/sec connection (not using the tools mentioned here), your site had a median page load time of 25.3 secs, which means half of the 10 tests were above that. The fastest load time was 9.1 secs (very poor) and the worst was 55.9 secs (ridiculous). Of course, those results come down assuming a faster internet connection (the median drops to 18.4 secs with a 20 Mb/sec fiber connection), but not everyone has a fiber connection. As I am sure you know, page speed is costing you $ if organic search traffic impacts your business results.
We do managed WP hosting and our pricing is $10 or $20/mo, and we'll move your site for free, but we do things differently from the other managed hosts you mentioned. Still, before you consider managed WP hosts, I think you'd be well served to streamline and declutter your site (or plan to do that as part of the move). Ask yourself if you need all of the scripts you are loading. Streamlining alone won't solve your problem, but that is in your best interest.
We would load your site much, much faster (without CloudFront, CloudFlare, or any caching plugins), but we'd really push you to do the streamlining. For a speed comparison, you can look at http://readyfolio2.wpperform.com/ ; that site's homepage is about 700 Kb, and first visit page load is about 1.2 secs over 20 Mb/sec fiber and repeat views (because we do use aggressive caching) are at 6/10's of a second. I think that's typical of the page speed we deliver, and that's what you need to be competitive. If your pages are loading in over 2 seconds, that's too slow.
Hope that helps.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberYou should be able to trigger a manual update check in your WP dashboard. If the update does not show up and you want to push ahead and if you are familiar with FTP (or preferably SFTP), you can download STC version 0.16 as a zip file.
Only go the download route if you are comfortable manually updating a plugin. Otherwise, be patient for the update to show up or consider other options (using another plugin or using Twitter's script directly).
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberEveryone has the same problem. Twitter updated its API, and the developer of the plugin hasn't updated his plugin to take that into account. Until he updates, it won't work.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberThanks for the kind words.
A short time ago, Otto released version 0.16 of STC, which now supports version 1.1 of the Twitter API, so you should be good to go.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberActually, let me clarify what I said about an update being forthcoming on STC. Otto very recently mentioned on Twitter he was looking at the updated Twitter API, and he mentioned on his blog late in 2012 he was working on an update to STC, but he removed the plugin from the WP repo some time ago because of, as far as I know, API issues. If you want to get Twitter working in a hurry, at this point you might need to explore other plugins or using Twitter's script directly.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberThe most likely cause is that in the past day or so, Twitter updated their API, and the code used to grab your latest tweets has changed. If you are using a script directly from Twitter, your best bet is to see if that script changed in light of their upgraded API.
Your tags say that you are using Simple Twitter Connect, and I know that Otto is working on an update, but I have no idea when it will be released.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberYour question is more complicated than I suspect you imagine it to be because of the SEO issues involved.
Since you have the domain dinnercreationscookbook.com, that domain will be an exact match domain for searches for the keyword phrase "dinner creations cookbook". Some believe that the value of exact match domains is declining, which is probably true. Still, an exact match domain will make ranking for that term easier, all other things being equal.
Therefore, you have to decide whether the value of that keyword and the boost from having an exact match domain is worth the time & expense of building out a site on the domain dinnercreationscookbook.com. Note that the exact match benefit is limited to searches for that exact phrase, and early on, the value will likely be low (since the book hasn't been published), but if sales of the book take off, the exact match domain can prove very valuable. If it is worth the effort, then your landing page question changes, because you'd likely have a page on your domain thedianekrause.com linking to your cookbook site. The page on thedianekrause.com wouldn't be a landing page, because you want the cookbook site to be the focus for that project. The page might describe you as an author or books you've written, but your goal would be to direct all traffic for the cookbook to the cookbook site.
On the other hand, if you decide the exact match domain is not worth the effort of building a 2nd site, you'd then build a landing page on thedianekrause.com, ideally where "dinnercreationscookbook" was in the landing page URL.
You can redirect every request to the domain dinnercreationscookbook.com to the landing page on thedianekrause.com, and your best bet is to work with your hosting provider to do that. If your host is using Apache servers, the simplest and fastest way would be to use redirects in an htaccess file.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMember@Herman - If you are on a webserver that runs Apache, I think your problem is related to mod_security, which is an Apache security module. It's a common problem with WP running on Apache servers, and it can trigger some bizarre outcomes, such as not being able to save a post because it contains a single, specific word. Here's an example.
I recommend you check with your webhost and see if you're running mod_security. If you are, ask your webhost to examine the mod_security logs. In most installations, these are in /var/log/apache2/mod_security on the server. If you got a 404 as a result of a mod_security block and logging was enabled, you should see a log entry that explains that. If you find that is the source of the problem, you'll have to work with your web host to adjust mod_security rules so as not to block the activity that was blocked. It's generally not a good idea to turn off mod_security altogether.
Hope that helps.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberI sent a tweet to Nathan Rice and he replied that a fix has been implemented so that when Genesis 2.0 goes to release candidate it won't add a structural wrap to the #inner div for XHTML.
@Tony - Your fix should also work and probably won't hurt anything in CSS if the structural wrap is removed, but once the structural wrap is removed by the change in Genesis core, it will be targeting a class that no longer exists so can be deleted.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
Bill MurrayMemberAfter taking another look, the problem is that even in the Genesis 2.0 beta 2, in lib/init.php on line 64, Genesis 2.0 is adding a structural wrap by default, whereas 1.9 didn't do that.
The change is in this line:
add_theme_support( 'genesis-structural-wraps', array( 'header', 'menu-primary', 'menu-secondary', 'site-inner', 'footer-widgets', 'footer' ) );
'site-inner' (or inner) wasn't included in the array under 1.9.2. Whether that's a design decision or a bug, dropping 'site-inner' from the array will fix your problem, but that involves modifying Genesis core, which isn't good. If you're developing on the beta and it's something SP plans to fix prior to release (which you might learn if you raise a ticket and point them to this thread), it might keep you on track for the short term.
Web: https://wpperform.com or Twitter: @wpperform
We do managed WordPress hosting.
-
AuthorPosts