Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Well after playing around with this, I think I have a workaround.

    (And the rabbit hole begins)..

    From the plugin’s directory, delete the latest (2.0.4) version. Then download the 1.8.0 version of the plugin and upload.
    (https://www.ads-software.com/extend/plugins/sitepress-multilingual-cms/download/)

    Go to your word-press plugin manager and activate the 1.8.0 plugin.

    Once 1.8.0 is activated, try doing an automatic update.
    You should get a message about it failing to update and the plugin no should longer being listed in the plugin manager (This is to be expected).

    Once you have successfully failed to update the 1.8.0 version, simply upload/overwrite the 1.8.0 version in /plugins/ with a fresh version of the 2.0.4 (or latest version to date).

    From here go back to the plugin manager, activate the plugin again and vola.

    Note, you might have to turn off permalinks and reset your custom permalinks when all this is said and done.

    I hope this helps others out there.

    I am getting the same exact problem.
    You are not alone, but I too have not found any solution!

    Please, where are the developers when you need them. ??

    Thread Starter devinrayolsen

    (@devinrayolsen)

    goldilock, no I did not and its very frustrating to the client to do these widget edits with no real prior html knowledge. This is why I was so happy when I found this plugin for them, but then my heart sunk when it failed to insert any type of media.

    Anyone?

    I don’t have the same issue of my backend control panel looking like that, but I do get a nasty error from FireFox that states:

    Error: The stylesheet https://www.devinrolsen.com/about/ was not loaded because its MIME type, “text/html”, is not “text/css”.
    Source File: https://www.devinrolsen.com/about/

    I have gone through and created a custom php.ini file (due to hosting setup) in my root dir of the site and changed the char type to not include quote like you suggested. But the error still remains.

    Here is the output of my header via FireBug.

    Date Tue, 13 Oct 2009 19:10:08 GMT
    Server Apache
    X-Powered-By PHP/5.2.2
    X-Pingback https://www.devinrolsen.com/xmlrpc.php
    Expires Wed, 11 Jan 1984 05:00:00 GMT
    Cache-Control no-cache, must-revalidate, max-age=0
    Pragma no-cache
    Last-Modified Tue, 13 Oct 2009 19:10:08 GMT
    Keep-Alive timeout=1, max=500
    Connection Keep-Alive
    Transfer-Encoding chunked
    Content-Type text/html; charset=UTF-8

    in my custom php.ini file I have added the two settings hoping it would fix my issue but thus far has not.

    default_charset = utf-8
    default_mimetype = text/css

    Anyone know whats going on? url is https://www.devinrolsen.com

    Thread Starter devinrayolsen

    (@devinrayolsen)

    Ahhh got it to work, went and tried to view some of my data tables, and it kept telling me that two of them crashed and needed to be repaired.

    Now I come from a zend framework background and web apps like magento who use huge amounts of tables and data passing between the application and the database.. never had and issue of needing to repair a data table before.

    Oh well its fixed now, that’s all that’s important!

    Thread Starter devinrayolsen

    (@devinrayolsen)

    anyone?

    Thread Starter devinrayolsen

    (@devinrayolsen)

    Hmm interesting but I don’t think this will work for me. There will be more than just the “Friends and Family” category we want to associate to the “Friends and Family” page.

    Meaning I have “Family Events” category that I would like to only be associated to the “Friends and Family” page..

    Also this solution would not prevent ALL posts from showing up on my home page.

    There must be a way to delegate where a post should show up and I would assume that this would be by associating certain category’s to certain pages.

    Just so I am clear here, this is not a feature already part of word press correct? Cause I have been looking all over the backend to no avail.

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