wpweaver
Forum Replies Created
-
Forum: Themes and Templates
In reply to: twenty ten weaver default width sizesThese widths are actually provided in the HELP file available on the Weaver theme admin panel.
Forum: Fixing WordPress
In reply to: change widget title colour in 2010 Weaver?This is very easy to do. You don’t have to change any style sheets. It can accomplished using the Advanced Options tab. There are examples in the snippets tab that address the CSS rules for widget titles.
There is a complete tutorial on adding CSS at the theme forum: http://wpweaver.info/forum
Forum: Fixing WordPress
In reply to: disable post highlighting on 2010 WeaverPlease address your support questions to the them support forum: http://wpweaver.info/forum
Forum: Plugins
In reply to: Changing Header Plugin for 2010 Weaver ThemeThis is discussed in the instructions that accompany the Advanced Options tab. It also has been discussed in the support forum: http://wpweaver.info/forum
Forum: Themes and Templates
In reply to: 2010 Weaver Header Problem2010 Weaver is based on Twenty Ten, and shares some attributes.
Part of the design of Twenty Ten, and indeed, WordPress 3.0, is the way new header images are handled. You MUST upload an image that corresponds to the size of the header image – 940×198 by default.
2010 Weaver allows you to change both theme width and height, which you should do before uploading a new header image.
Otherwise, if you provide an image that is smaller than 940×198, which your imageshack image is, then the image will be upsized from the original to 940×198, which is why it is fuzzy.
A photo editor will usually do a better job of upsizing, but you really should start with an image greater than or equal to 940×198 and downsize it to fit.
If you want the best looking image, then you have to work with the rules.
The .one-column rule is for the page template when you create a new page. If that is what you are using for your one-column pages, then just adjusting the .one-column rule should fix it.
If you’ve instead used the Main Options sidebars setting, you would need to adjust the #container, #main, and/or #content rules – there are more details on this in the snippets.
Forum: Themes and Templates
In reply to: 2010 Weaver SupportI will have to check this out. Please add a post to http://wpweaver.info/forum to get a follow up.
Forum: Themes and Templates
In reply to: 2010 Weaver SupportYou should really never have to modify CSS files. You should use the <HEAD> Section on the Advanced Options tab to over-ride CSS rules. Then you won’t lose anything when you upgrade.
Forum: Themes and Templates
In reply to: 2010 Weaver SupportYou’ve either picked no sidebars from the Main Options panel, or you’ve used the .one-page template when creating your pages.
Forum: Themes and Templates
In reply to: 2010 Weaver SupportActually, turning off the title of all static pages can be done in the Weaver theme using:
#content h1.entry-title {display:none;}Posts titles are h2, so they won’t be hidden.
—–
And I don’t know what is going on with your download from the site. I just downloaded to both a Mac and a Win7 machine, and the zip file unpacked fine. Perhaps some temporary file issue. I did switch hosts last week, and there may have been a small window when various DNS servers were out of sync. Sorry if that caused issues, but it is not very easy to try to switch hosts for a live site.Forum: Themes and Templates
In reply to: 2010 Weaver SupportHow to do this is already included in the CSS snippets included with 2010 Weaver:
If you want to hide the title of a specific page, you use the WP ID of the page (both posts and pages have ids – you can get the page id from the Edit Page/Post address bar – it will show as ?post=id). To hide a specific post or page, use this (this example will hide the title of page with id=3, you have to determine the id of the post/page whose title you want to hide):
#post-3 .entry-title{display:none;}
Forum: Themes and Templates
In reply to: New WP3 Twenty Ten child themeThere also is a plugin available that will perform this action without needing any coding. Send an e-mail via the http://wpweaver.info about/contact page to request a copy.
Forum: Themes and Templates
In reply to: WordPress.org server problems and 2010 WeaverI generally don’t check wp.org very often – most of the support is done via http://wpweaver.info.
Reinstalling WP would delete all your previous pages and posts (unless you restore the database.)
Don’t know exactly what happened with your site, but renaming a theme directory does not hide it from WordPress – so if a file had gotten corrupted (like via the broken upgrade described in this thread), simply renaming will not remove the errors. You have to delete the theme subdirectory.
With Weaver, all your settings will remain intact when you reinstall the theme.
It looks at the moment your site is up – and it looks very nice with the flower background and transparent sidebars. I sincerely apologize for your difficulties, and hope things go better now that this upgrade issues seems past.
Forum: Themes and Templates
In reply to: IE 9 Beta Breaks Twenty Ten?Too bad – makes it hard to build a theme not knowing if IE 9 will remain broken on something that every other browser, including IE 8 and apparently previous versions of IE, gets right.
@esmi – who do you mean knows about the issue – Twenty Ten developers, or Microsoft? Hope it is Microsoft, and that they understand it is their problem to fix.
Thanks for the info. Good to know it isn’t just me seeing this.
Forum: Themes and Templates
In reply to: WordPress.org server problems and 2010 WeaverDid that, and the new one seems to be OK.
Just for more information, it turns out that the system generates copies of a theme’s .zip file (any theme available here) on the fly, and puts copies in /tmp directories on different servers. Depending on load balancing and whatever, one gets the file from a different server in a random fashion.
Apparently one or more servers have generated broken copies of the theme .zip files, and thus the issue. The Piano Black theme suffered from the same issue, too, although it seems to have cleared up now.