Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter pauldotmac

    (@pauldotmac)

    I didn’t want to restrict access to specific tables just grant them access to the Tablepress plugin. Got it working now thank you.

    Thread Starter pauldotmac

    (@pauldotmac)

    The description field includes a link to an external php file that generates a pdf document. Some people seem to be having caching issues with the version of the pdf file that gets generated so I thought I might add a random value pair to the query string to make sure the correct latest version of the pdf file gets generated. About the time you posted it occurred to me that maybe I could do it with a shortcode.

    Thanks for the quick reply.

    Thanks

    Paul

    Thread Starter pauldotmac

    (@pauldotmac)

    Don’t what happened but it now working. Thanks.

    Paul

    Thread Starter pauldotmac

    (@pauldotmac)

    Hi,

    Thanks for the quick response. I’ve made the change and I no longer get the error message but the passed parameter is not being picked up.

    The line $output .= ‘<h1>Assessment Planner – ‘.$locn.'</h1>’; just produces “Assessment Planner – ” without UNITED KINGDOM.

    Thanks

    Paul

    • This reply was modified 4 years, 6 months ago by pauldotmac.
    Thread Starter pauldotmac

    (@pauldotmac)

    Excellent, thank you for the rapid response and the alternative solution.

    Should have spotted the missing “<“, simple mistake, but thank you

    Thread Starter pauldotmac

    (@pauldotmac)

    Excellent, worked as indicated.
    Thank you.
    Paul

    Thread Starter pauldotmac

    (@pauldotmac)

    Ok, I understand the bit about havng the same slug but if I didn’t actually initiate the update, either manually or byt setting up some auto update routine, how did it happen?
    Thanks
    Paul

    Thread Starter pauldotmac

    (@pauldotmac)

    [RESOLVED] I’d mentioned that I had changed the tables’ prefix. The site is for a symposium that happens every 2 years; so last year’s prefix was 2017_ and next year’s prefix (for the new site) will be 2019_. There are several fields in the 2019_options and 2019_metadata tables that made cross reference to 2017_* fields or data. I simply went through them one by one and changed 2017_ to 2019_ and the dashboard now loads. Strange that on all the sites I visited to resolve the problem none mentioned about table prefix changes – although https://www.elegantthemes.com/blog/tips-tricks/locked-out-of-wordpress-4-solutions-when-you-cant-access-wp-admin did, when talking about the structure of the user_meta table state “meta_key — Here, write wp_capabilities”, wp_ is the normal prefix for wordpress tables – it was this that set me think about the table prefix. If, like me, you change it then there are consequences.

    Thread Starter pauldotmac

    (@pauldotmac)

    I eventually solved this, it is all to do with the .htaccess file. Nothing to do with the mimetype at all. Try deleting the .htaccess file or removing stuff to do with the live version that is not applicable to the localhost version; rewrite rules for directory names etc.

    Paul

    Thread Starter pauldotmac

    (@pauldotmac)

    Now this is weird. I’ve downloaded versions of the 2 errant local websites from the webservers onto my local pc and one of them works. What’s even more strange is that I copied the index.php file from the working downloaded directory to the none working directory and it doesn’t work, I get the original message about wanting to open the file.

    Any suggestions?

    Thanks

    Paul

    Thread Starter pauldotmac

    (@pauldotmac)

    Thank you for looking at this but it didn’t work. Also I get the same problem in IE so it is not linked to the rdf file in Firefox. Also my other php based websites that are not WP based all work, so the mimetype recognition is working.

    Inside wp-includes/version.php I have
    $wp_version = ‘4.5.4’;
    $wp_db_version = 36686;
    $tinymce_version = ‘4310-20160418’;
    $required_php_version = ‘5.2.4’;
    $required_mysql_version = ‘5.0’;

    and
    $wp_version = ‘4.4.5’;
    $wp_db_version = 35700;
    $tinymce_version = ‘4208-20151113’;
    $required_php_version = ‘5.2.4’;
    $required_mysql_version = ‘5.0’;

    For the 2 WP sites that don’t work and

    $wp_version = ‘3.6.1’;
    $wp_db_version = 24448;
    $tinymce_version = ‘358-25336’;
    $required_php_version = ‘5.2.4’;
    $required_mysql_version = ‘5.0’;

    for the WP site that does work.

    My winamp installation is
    winamp server 2.4
    Apache 2.4.4
    PHP 5.4.12
    MySQL 5.6.12

    This is not a browser level problem. I think you are right it is a mimetype recognition issue.

    Thanks for all your help and looking at this

    Pau

    Thread Starter pauldotmac

    (@pauldotmac)

    Hi,

    Thanks for the reply. I’ve done what you suggested the .htaccess file now says

    AddHandler application/x-httpd-php54 .php .php5 .php4 .php3

    but to no avail. But why would the 2 sites stop working? A couple of weeks ago all was fine.

    Any other suggestions? Re-install winamp server?

    Paul

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