Forum Replies Created

Viewing 15 replies - 1 through 15 (of 121 total)
  • Thread Starter thelazygeisha

    (@thelazygeisha)

    @ Gangleri

    Hmmm, so this was something in the 2.2+ series? Interesting. Tho, my understanding is that all site PW were hashed and stored in one of the database tables, so my initial panic was just that, panic. I was just curious as to why on earth anyone would try to be direct entering a url to a php file — I mean, I know it’s a server side language — but it was late and I was somewhat bleary. I was really just curious about some other hole I might not have been aware of.

    @ Whoo

    Hey there! (waves)

    Thanks much for the answers!

    nina

    @moshu

    I stand corrected on that point, however, wasn’t that easier than:

    Just read the documentation:

    Maybe it’s me, it probably is, but the RTFM vibe always puts me off this place, and perhaps my caution in handing people the shovel is misplaced too.

    Every once in a while I’ll try to help, but maybe even that’s become too much trouble than it’s worth.

    But, that’s it for today. TTFN.

    @sandal_woods

    I can’t see any borders either, but what it sounds like to me is that your images have an embedded hyperlink, which likely means that when you’ve pathed to an image your theme is calling for, you’ve formatted the link incorrectly.

    The ‘blue box’ around an image indicates that there is a hyperlink associated with it – if I’m understanding your description of your problem correctly here. You need to check the formatting of your links if this is indeed the issue.

    @rickonline

    You really need to have an understanding of formatting php and writing php enabled pages here in order to make this work.

    Without knowing your theme; there is likely something called single.php in your theme files (or something else as someone else suggested).

    When you create a new page within WordPress, you’ll see a drop down dialog box which calls for you to select a template. Have you actually verified that your theme doesn’t already contain this option for you? If it doesn’t, you’re going to have to create the template yourself, or, as I suggested, contact the theme’s author for further mods.

    What you have to understand is that there is no one way to do this… every theme is different, and there could be dependencies in there which you’re unaware of.

    Tho, I’m a big believer that you learn by mistakes, so, you could start here.

    On Edit: You’re also going to need the software tools necessary to write php pages.

    @sammy123

    You’re not reading what I wrote. There is no way to automatically repath every image link in every single post on your blog.

    You can do this:

    1) You can upload all of your images into your media gallery, manually

    2) You can manually edit every single post and replace the image currently there with an image you’ve uploaded into the media gallery.

    Or, you can leave it alone and just go forward. Your site does need that root/image directory, so I wouldn’t be thinking about making it go away if I were you. I mean, the new Media Gallery in WordPress is nice, but it isn’t Picasa, kwim? You really only need it for future posts, unless you use the same image over and over, and if you do, just upload it into the gallery and use as you need. It isn’t hurting your site to have your older image links pathed to the root/image folder.

    @danielhv

    Sounds to me like there’s an issue with your theme. Are you 100% positive that your theme and template are WordPress 2.5 compatible? See, some of this reaches back into the history of WordPress when widgets were done with a plugin. Widgets are now part of WordPress itself.

    The way to test this is to work backwards. Does the problem follow if you switch to the WordPress default theme? If widgets do work in the default theme then you have your answer.

    @ranessirhc

    I do understand your frustration, but I think taking a step back is better than venting in the forums. This sort of thing often happens in the open-source software community – people aren’t being paid to answer support questions, so you’re sometimes at the mercy of whomever happens to be around — and trying to assign blame never works, but being nice to people who might be able to help you will.

    I think the first step is to understand the error. Try this.

    I don’t know what you’re doing with your site, but Google is telling you what the problem is:

    When we tested a sample of the URLs from your Sitemap, we found that some URLs were not accessible to Googlebot because they contained too many redirects. Please change the URLs in your Sitemap that redirect and replace them with the destination URL (the redirect target).

    Did you move your sitemap.xml or sitemap.xml.gz files when you upgraded? Did you try reinstalling the plugin? Did you try creating new files and rebuilding your sitemap again?

    Or did you consider that this could be a Google problem? They do happen you know.

    @ranessirhc

    Am I always asking the wrong way or something?

    Well, yeah, you sorta are.

    I mean, you’re having a plugin problem, not a site problem. The issue isn’t WordPress 2.5, it’s how you’ve got your plugin configured, or not configured in this case it seems.

    This is an issue you’re having with Google, not so much WordPress. I would suggest contacting the Plugin Author, Arne Brachhold, he’s a nice guy and ask him what you’re doing wrong.

    @rickonline

    The best suggestion for me to make here is for you to contact the theme’s author for further mods. I mean, I’d hate to be responsible for giving you the shovel here! Unless someone else can offer a better suggestion.

    Good luck!

    – nina

    @danielhv

    Some of those “widgets” are not really widgets. If you examine your theme files, you will likely see one named sidebar.php — check and see which ones are written into the code and won’t let you modify them.

    You can go into the design settings all day long and they’re never going to go away that way if they’re written into your template, and reverting back to 2.3.3 will certainly never work.

    The code which generates those things in your sidebar is likely there, tho I caution you on commenting on php files unless you know what you’re doing, or you run the risk of creating php errors.

    What do you want? A blank page with no sidebar at all? You should create a template for a blank page and add it to your theme, then republish whatever page you’re trying to fix. Unless you really don’t want a sidebar, and in that case I don’t know what to suggest.

    @wyffgoal

    yw.

    @sammy123

    All of the media content in your posts, such as images, etc. have links pathed back to your root/image directory. I don’t believe there’s going to be a one click solution to repath every link to every image in every post. You can go forward, but not backwards here.

    So this:

    Is there any way to retain the file location and name, but append the needed “post_type attachment” that WordPress does usually via it’s upload manager?

    No, not so much. But, you can repath the upload directory for future uploads, but you won’t be able to read all of that metadata and thumbnails into the media gallery from what is already loaded in root/images

    @ehjay

    You need to talk to your host and make sure you have permission to modify php.ini

    Some hosts may let you look, but not touch – and may have rules about modifying those settings which could impact any kind of shared host environment.

    @rickonline

    You need to create a template of a blank page without the sidebar and add it into your theme files.

    Then, when you re-publish that particular page, you need to change the template.

    @fighttrend

    Some Image uploader issues are discussed in a sticky thread here.

Viewing 15 replies - 1 through 15 (of 121 total)