Forum Replies Created

Viewing 8 replies - 76 through 83 (of 83 total)
  • Thread Starter macksix

    (@macksix)

    I don’t see Meow Apps on production site but I do see it on the dev site, so I probably need to deactivate and reactivate it on the production site to get it back on the menu.

    Thanks

    Thread Starter macksix

    (@macksix)

    If this is in some sort of settings panel, I can’t find it. I can’t even find any settings for it at all. I found something under Media but no settings.

    There is no Meow Apps item on the dashboard either.

    • This reply was modified 7 years, 1 month ago by macksix.

    If you don’t delete the .opcache folder it may not work putting the settings in the php.ini file, but settinga from other host in your php.ini may not work right, so you can remove all the settings in it and just put the entries I posted above to see if they work. You also need the .htaccess entry to point to your local php.ini file for the entries to work.

    This should be at top of .htaccess

    SetEnv PHPRC /home/your_username/public_html/your_wordpress/php.ini

    I have since moved to Incendia Web Works.

    • This reply was modified 7 years, 2 months ago by macksix.
    • This reply was modified 7 years, 2 months ago by macksix.
    Thread Starter macksix

    (@macksix)

    Edit: removed this reply.

    • This reply was modified 7 years, 3 months ago by macksix.
    Thread Starter macksix

    (@macksix)

    Mirrored the site, turned off all plugins and activated Twenty Seventeen and the Visual and Text editor tabs still do not show for her, but WordPress 4.8.3 works for her.

    • This reply was modified 7 years, 3 months ago by macksix.

    Great, I was looking for the same solution. It would be nice to be able to select a row and it display single column while leaving others 2 column. For instance a row that is just one text widget with a divider could be selected to display 1 column while the others above or below it with more than one widget would display 2 column.

    • This reply was modified 7 years, 3 months ago by macksix.
    Thread Starter macksix

    (@macksix)

    Well I have used it with no problems on two others sites, but this site does have W3 Total Cache that does have database caching, but it is checked to not cache database for logged in users. I did not realize it had that feature. I did however wondered at the time if it was showing me a cached page, so I had clicked the button to “empty all caches” to no avail. But is is possible it was not clearing the database cache since it was not supposed to be caching for me in the first place being that I was logged in.

    Thanks!

    Mark

    • This reply was modified 7 years, 4 months ago by macksix.
    • This reply was modified 7 years, 4 months ago by macksix.

    I had these error messages on siteground on a fresh default WordPress 4.8 installation. The first error message was on the home page and in Admin.

    Warning: array_merge(): Argument #2 is not an array in /home/username/public_html/wordpress/wp-includes/load.php on line 63

    Warning: Cannot modify header information – headers already sent by (output started at /home/username/public_html/wordpress/wp-includes/wp-includes/load.php:63) in /home/username/public_html/wordpress/wp-includes/option.php on line 837

    Warning: Cannot modify header information – headers already sent by (output started at /home/username/public_html/wordpress/wp-includes/wp-includes/load.php:63) in /home/username/public_html/wordpress/wp-includes/wp-includes/option.php on line 838

    Also, the Add Theme (theme-install.php) page would not work with an error message with no specific reason why.

    After a few rounds with support, tech finally did this to solve it:

    I think that I was able to resolve the original issues that you have described.

    What I did was to add the following lines to the public_html/wordpress/php.ini file:

    Code:
    output_buffering = On
    opcache.interned_strings_buffer = 16
    opcache.memory_consumption = 400

    The first line will correct the headers already sent warning message which is due to code that is not sending HTTP headers in the beginning of the script that is being executed. Unfortunately, I cannot tell which script may be causing this warning.

    The other two lines increase settings of the Zend OpCache module which is active by default with all PHP 7.x versions.

    Please have in mind that I also had to rename the .opcache folder that is located in the /home directory of the hosting account.

    Let us know if there are still issues that we should address.

Viewing 8 replies - 76 through 83 (of 83 total)