Forum Replies Created

Viewing 15 replies - 1 through 15 (of 23 total)
  • Disconnecting the permalink/slug from the title UI was a horrible decision. Why introduce a regression that major at all?

    It just requires retraining users for no benefit, and it’s in a far less obvious place.

    The sidebar also can and will get very crowded on a lot of sites in practice with custom fields and whatnot.

    I don’t have a work around built either.

    Please let me know if you come up with something.

    Agreed, this is a huge miss in the new version.

    With or without drag/drop this feature is a must-have for sites with larger redirect sets.

    I just got a bunch of the same errors while updating posts programatically.

    PHP Fatal error: Uncaught exception ‘Exception’ with message ‘Unable to delete files. Rename failure on tmp directory: /opt/website/prod_sites/name-of-site/wp-content/cache/quick-cache/cache/https/www-name-of-site-com.’ in /opt/website/prod_sites/name-of-site/wp-content/plugins/quick-cache/includes/share.php:1566\nStack trace:\n#0 /opt/website/prod_sites/name-of-site/wp-content/plugins/quick-cache/includes/share.php(1357): quick_cache\\share->delete_files_from_host_cache_dir(‘/^\\\\/blog(?:\\\\/in…’)\n#1 /opt/website/prod_sites/name-of-site/wp-content/plugins/quick-cache/quick-cache.inc.php(1322): quick_cache\\share->clear_files_from_host_cache_dir(‘/^\\\\/blog(?:\\\\/in…’)\n#2 /opt/website/prod_sites/name-of-site/wp-content/plugins/quick-cache/quick-cache.inc.php(1029): quick_cache\\plugin->auto_clear_posts_page_cache()\n#3 [internal function]: quick_cache\\plugin->auto_clear_post_cache(4782)\n#4 /opt/website/prod_sites/name-of-site/wp-includes/plugin.php(505): call_user_func_array(Array, Array)\n#5 /opt/website/prod_sites/name-of-site/wp-includes/post.php(5464): do_action(‘clean_post_cach… in /opt/website/prod_sites/name-of-site/wp-content/plugins/quick-cache/includes/share.php on line 1566

    Usually, look for stylesheet or script tags from the theme.

    That site does not appear to be a wordpress site.

    Yup, I know – but I don’t think it’s obvious.

    We’ve had clients experience similar frustrations to the OP. Text vs. TinyMCE causes issues.

    Similarly, wpautop is fine if you aren’t putting markup into the editor(s), but causes a lot of grief if you expect it to be unfiltered HTML you are entering.

    I’ve also noticed that switching back and forth between tinymce and the text editor can cause some things to change, because content you put into the text editor gets parsed by TinyMCE when you switch to the visual editor.

    Basically, WordPress filters the markup you put into the text editor, this can cause issues with raw markup you put in, especially when it contains line breaks.

    The text editor isn’t really an HTML editor, it’s more like a .txt editor that allows you to use some tags.

    The content you put in is still filtered. The text area doesn’t really behave all that differently from the tinymce editor.

    You could try disabling the wpautop and wptexturize filters, but that isn’t without issues either – especially since you aren’t starting with a fresh site here; other content you previously added likely relies on those filters to look right.

    If you don’t, you will get duplicates created with new filenames. It won’t hurt anything, but the existing files still won’t be used.

    instead of image.jpg, you’ll end up with image1.jpg

    I’m not sure what you mean about new articles showing up in the /uploads folder… That should just be images and other media you have uploaded.

    As far as your old images being in a folder on the server, but not showing up…that’s because you have missing/corrupt data.

    Having the files on the server is a start, but WordPress is totally unaware of them without the database records that go with.

    If you have a good .sql backup (and know your way around databases), you could import the backup into a new empty db, and then selectively export from there the tables you want to copy over to your production db.

    If that is outside your skillset, at this point you might be better off trying the support for your hosting account and see what backups they have, maybe they can restore your entire site to a previous working version.

    In the future, maybe take a look at VaultPress, it’s cheap and well worth it.

    What sort of database backup do you have? A .sql file?
    WordPress Exporter XML file?

    You need to restore your database if you have a backup (hopefully).

    You have the theme, plugins, and uploaded images, but not the post/page/media data currently.

    You should backup and run a core update asap.

    Can you access the admin?

    If so, try running a core update and see if that fixes it.

    If not, take a look at the manual (FTP) update instructions in the codex.

    Hope you have a backup of all this.

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