But this is really most unintuitive “feature”: what if I want to change the theme, and new theme uses different image sizes? What if I have to change layout and to reduce sidebar images, for example? I have to resize them all? Again? And have to install plugin for that? Really annoying and doesn’t work as expected. At least for me.
I agree that it’s not ideal – and at times very annoying. The fact that  it doesn’t generate the images on the fly,  it generates all registered sizes even if they’re not necessary (required due to ), and  it won’t upscale are huge drawbacks. If I were creating a personal site I’d still use timthumb (never had an issue setting it up). But as far as themes go, because its so much easier for users to just have everything work out of the box (even if the way it works is not optimal), I think I’m opting for the WP thumbnail system.
It just comes down to implementing the path of least resistance for buyers I think.
Also, you can write a wrapper to the WP function to make it function more like timthumb. But hopefully they’ll improve this in the future
Perhaps it is hard-coded in the header file? Look for the h1 with the #theme-logo anchor in header.php and see what’s there. If it says “livepuse” in plain text then just change it to your site name. If there’s some PHP , it must be pulling from an option somewhere in the theme panel.
crozer saidI’m not convinced about this. As I said in the reffering thread, I’ve added all image sizes that I need and WordPress is returning image paths to the original image with width/height attributes. Try for yourself: right click on the thumbnail image and click view image. It displays larger image than thumbnail.
And wrong because it DOES scale images. That’s what the the add_image_size is for. After the X and Y values, you specify whether you want the images proportionally cropped (scaled), or hard-cropped.
I can confirm what crozer said. If you’re using post thumbnails and
add_image_size properly, WordPress definitely resizes the image and creates a brand new scaled and cropped image file. If your implementation is not generating new images, perhaps you don’t have the required PHP libraries installed (GD) ?
set_post_thumbnail_size function, on the other hand does not resize the image. Perhaps that’s what you’re referring to?
Also, WP doesn’t produce the scaled images on the fly like timthumb does – only on upload. So if you add new image sizes you won’t see them for previously uploaded images unless you rebuild the images. Try http://wordpress.org/extend/plugins/regenerate-thumbnails/
Also, this article is very useful: http://www.studiograsshopper.ch/web-development/wordpress-featured-images-add_image_size-resizing-and-cropping-demo/
Usually you change the title of your site by going to Settings > General > Site Title, but there may be a different way that you do it for that theme (in the theme options). It should be in the instructions if so.
If not, the best way to get theme-specific help is to contact the author directly http://themeforest.net/user/manu3l9816
The issue described in the video is that the zip you download from ThemeForest includes files apart from just the theme. For example, PSDs and Help files. The “theme” itself is contained inside that zip file.
So the first step is to unzip the file you downloaded. Check out what’s inside. Usually there are detailed instructions on what you need to do to upload and install the theme. Sometimes, there is a zip inside the zip that is specifically intended to be uploaded through the WP theme installer. Other times the theme is just in a folder. In this case, you can upload the theme via FTP , or zip it yourself and upload it that way.
Remember, the style.css file will need to be in the folder that you upload to wp-content/themes (whether it is zipped or not).
If that doesn’t help, I’d recommend telling us what you’ve done so far, and posting a list of the contents (or a screenshot) of your unzipped file.
Hope that helps,
I thought this feature would be useful especially for a theme framework used primarily by developpers
Perhaps Personally, as a developer, I really dislike the WP code editor (like duotive mentioned). I would rather develop in my IDE of choice than use the in-browser editor. But maybe that’s just me
I think that’s a good point. And making access to the code easier for those who don’t know what they’re doing may be asking for trouble. I think in many cases, if a user can’t use FTP , they probably shouldn’t be messing with the JS You might create more headaches than you solve.
On the other hand, if you built a real in-browser text editor (not just a textarea like the built-in WP code editor), with syntax highlighting, etc, that might have some real value.
In any event, it’d probably be better to write the code to be extensible and then allow users to make modifications without editing the core (like bfintal said, small areas with additional JS is probably a better solution).
Thanks, I’m actually using Waypoints (it’s excellent) as a component in the plugin (already completed), but looking for a good name to describe this specific application of it