Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thanks so much for your reply. I checked out the link. It looks like you’re working on a lot! In the meantime I think I’m going to stick with the old editor until more of it is sorted out.

    Actually, the more I’m working with images the more problems I’m coming across. For example, if I edit the html of an image to add, say, data-pin-nopin=”nopin”, then I can no longer have this image as a block. Or rather, if I try to save it as a block the html I added disappears. This is a problem, since once I edit the html of an image I can no longer see the image in the visual editor. I’m not sure how to resolve this since I have no idea how the blocks are built. But I’m sure for a lot of us, being able to edit the html of an image is essential.

    ETA I just noticed that this thread has been marked as resolved, so I’m going to start a new one.

    I’m not really understanding this answer, and I don’t think that the changes made after clicking on the pencil are carrying over into the html of the post. When I click on the pencil and go to the image I’m trying to edit, the alt text that I added in the block is not there, and if I change the title after clicking the pencil, that information does not make it into the html of the block. The two different editing processes don’t seem to have anything to do with each other, so unless I want to code it in, there doesn’t seem to be a way to add a title to an image in a block. Or am I missing something?

    • This reply was modified 1 year, 6 months ago by selfishmom.

    Thanks! As long as there’s some kind of link or credit, either to my blog ( or to my twitter account (@AmyOztan), go for it.

    Thank you for your response. I have many images in my posts, but I want to either choose which one I’m using, or use one that isn’t in my post. And for the ones that have borders, cropping makes them look bad. Here’s an example of an image I’ve made especially for sharing on Twitter. Since it has a border, cropping could have looked much worse (luckily it wasn’t bad–looked worse in the authenticator–but I would like to use the correct size in the future).

    Thank you for your quick answer. I did not know that I had Yoast Twitter Card support turned on, so I’ve turned that off. As for the size, I think the images really need to be 2:1 in order not to get cropped. 280×150 or any multiple of that leads to a little bit of cropping. I can’t confirm that 100% until I make a new post, but I do know that 280×150 will be cropped.

    The major piece that I was missing was what to do with the custom field information on each post. I had it set up correctly in the Twitter Card option, but I could not figure out what the next step was – how to indicate which picture to use in each post. I finally put it all together.

    For anyone else who can’t figure it out: Upload the image that you want to use to your post. You don’t have to place it in your post, you just have to upload it and get its URL.

    If the Custom Fields editor is not showing for you in the WordPress editor (it wasn’t for me), you’ll have to go to “Screen Options” in the top right corner and add it. Click “Enter New” under “Name.” Then, put “images” (or whatever word you set up in the Twitter Card options) in the “Name” field, and put the URL of the image in the “Value” field. Add the custom field, then update or save your post, and the correct image should show on Twitter.

    Done! Please let me know if you don’t receive it.

    Sure, can I email you?

    Just tried that last one and brought my site down. I added it before the line that said # END WordPress. I don’t know where my .ini files is and I’m reluctant to mess with it too much, before I do something that I can’t undo.

    Just tried it again and this time the fatal error was this: “Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 262144 bytes) in /home/content/c/i/c/cicek1/html/selfishmom/wp-includes/wp-db.php on line 1710”

    I followed the instructions for changing the wp-config file so I’m not sure what to do, but you’re right, it doesn’t seem to be changing.

    I added “define(‘WP_MEMORY_LIMIT’, ‘128M’);” to the wp-config.php file.

    Hi Brecht, thank you for your speedy reply!

    I increased the memory limit to 128.

    The error is this: Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 35 bytes) in /home/content/c/i/c/cicek1/html/selfishmom/wp-includes/wp-db.php on line 1710

    Each time the size is different (usually much bigger than 35 bytes), but “line 1710” is always the same.

Viewing 12 replies - 1 through 12 (of 12 total)