Subrata Sarkar

Hi @aniketji, the problem lies here, in cool-timeline-pro/admin/class-cool-timeline-posttype.php.

function ctl_template_redirect()
{
   if(is_post_type_archive('cool_timeline' ))
   {
      wp_redirect( home_url( '/' ) );
      exit();
   }
}

I don’t really understand the purpose of this forced redirection. I have to comment out the function body in order to get search page to post back on itself and bring me the desired filtered result!

However, I also understand that updating the plugin will overwrite this!

If this is done on purpose, i would love to know the use case. Otherwise, I feel this can be omitted or rewritten to overcome the problem. Because, a search can easily be a requirement since timeline is registered as a post type like page and post!

Thank you!

Hi @aniketji, thank you for your reply. I am not asking for any custom support! All I want to know is whether there is any additional settings that need to be set up inside the plugin for the above to work correctly.

Because, it is very strange that all except cool_timeline filter is not working!

Thank you!

Actually I figured this out! ??

Hi @roxannestoltz

Thanks for your help! The solution is sort of working. To be exact after clearing all the recommended caches, I was expecting an immediate effect.

However, it is actually taking some time even after applying the solution before the warning completely goes away.

But this information is definitely helpful.

Regards,
Subrata

Hi @robelemental
Thank you for your reply!

I went through the article, but could not make myself clear about the issue I am facing. The specific line of code you mentioned, is calling a method tribe_get_event(), which is declared in plugins/the-events-calendar/src/deprecated/functions.php file.

tribe_get_event() is calling two static methods check_exists() and get_args() which said to be declared inside the class Tribe_Events_Meta_Factory. In my case, the class is reported to be missing!!

Here is the starting line of the full error message that I sent earlier:

Fatal error: Uncaught Error: Class 'Tribe__Events__Meta_Factory' not found in /app/wp-content/plugins/the-events-calendar/src/deprecated/functions.php:113

I tried to navigate to the definition of Tribe__Events__Meta_Factory, but it is not there at all!

Which left me with the question, exactly what I have to modify and where!

Hi @abzlevelup Thank you for looking into this. ??

Hi @vmarko, as per your suggestion, I have downgraded the plugin from 2.1.8 to 2.1.6 and removed robots.txt successfully. No issue has been popped up since then.

Thank you!

Thank you @vmarko for your suggestion! I will do the same

I updated W3TC only yesterday to 2.1.8 and the following robots.txt error appeared on the screen

FTP credentials don’t allow to write to file /var/www/xxxx/robots.txt
W3C Total Cache Error: Files and directories could not be automatically created to complete the installation.
Please execute commands manually or use FTP form to allow W3 Total Cache make it automatically.

Following is the content of robots.txt file

# BEGIN W3TC ROBOTS
User-agent: *
Disallow: /wp-content/cache/
# END W3TC ROBOTS

And most importantly, the plugin page becomes completely blank! Then, I had to go use the recovery mode and deactivate the plugin!

According to @vmarko I should have experienced this in the ealier version but most interestingly I never seen this messaage before updating to 2.1.8.

How can I get rid of this issue? I have a feeling that even 2.1.8 could not resolve the issue completely. Is this entirely an error coming from W3TC or other plugins could be responsible for this. If yes, could you figure out yet what might those be? Because this is very important to have the caching working properly!

• This reply was modified 3 years, 2 months ago by Subrata Sarkar.

@evolvingdoor you are right. I had faced the same problem. If you have FTP access, remove the plugin from there by going inside wp-content/plugins and remove php-compatibility-checker directory.

The good thing is php-compatibility-checker does not create any additional table in your system, however, if you have run the scan at least once, the plugin would add some entries in your wp_options table.

You may remove those records manually from the table by executing a query: DELETE FROM wprc.wp_options WHERE option_name LIKE 'wpephpcompat%', but if you are not comfortable in running queries or you don’t have access to the database, just leave them as they are. They wouldn’t have any impact on your system since you have already deactivated and removed the plugin completely.

The options_name that are added after you run a scan are:

wpephpcompat.lock
wpephpcompat.numdirs
wpephpcompat.only_active
wpephpcompat.status
wpephpcompat.test_version

Thank you @ishikiriyama.
Yes, that is one solution that could be used the bypass the issue.

Regards,
Subrata

Thank you very much for your quick and nice reply!

“The plugin/theme was skipped as it was too large to scan before the server killed the process.”

What is the exact reason for this error message? What is the workaround for this? Is the process really being killed or this is a kind of default fallback message which comes from the checker plugin if any ERROR related to PHPComatibility is encountered? If so, there should be a proper message rather than just showing “Unknown”!

I am getting this for a number of plugins installed in my site. Is it safe to update to a newer PHP version? If not, how can I resolve this problem?

On another note, I was expecting a way to control select one or multiple plugins rather than running the script on all/active plugins and themes. But as of now, there is no no option like this.

For me “some” turns out to be “nothing”. I am expecting at least the icons will come up!!

@markwolters I tried everything but there was no luck!