MESO

We just updated to the newest version, however I cannot find the option you mentioned.

Hi, a response would be great.

We have just updated to v5.4.0 and have not been able to find the option to enable the warning. The only thing we could find was the empty misc section, but this was already there. The changelog does not list anything similar either.

• This reply was modified 4 years, 9 months ago by MESO.

It seems wildcard allowed filetypes are no longer allowed. This might be something worth noting in the changelog.

> However, from the next update, we are adding an option to show warning for outdated template files.

We have updated to 5.3.7 recently and were unable to find such an option. Could you help us with where to find it?

@Shahjada would you kindly tell me how to update them or elaborate on what part exactly is outdated and in what way? You can also just annotate it in the files using something like <!-- ToDo --> or similar

• This reply was modified 4 years, 10 months ago by MESO.

> issue is related to your custom theme

but as stated in my initial question, it was regarding the /uploads/ page. I also specifically asked for the reason of the issue in the theme, since you mentioned it. Unfortunately you have not yet provided an answer regarding what we can do to solve this issue.

The newest version we have access to is 5.3.5, which is also the version installed. In this version clearing the cache does not help much. When can we expect the update with the fix to be available to us?

• This reply was modified 4 years, 11 months ago by MESO.

> that is a permanent solution :). So, it will not cause any trouble from now on.

unfortunately it is not. It’s not a solution at all since in production the success-rate is even lower than 13/20, it’s probably closer to 10%.
You mentioned an issue with our template. Could you elaborate on that or fix it?

Do you have any idea how we can make it work 100% of the time?

Could you please elaborate on what issue it was so we can fix it in production? Also the fix does not work some of the time (I tried reloading 20 times and it worked only 13 times)

• This reply was modified 4 years, 11 months ago by MESO.

I have version 5.3.5 installed and Cleaning cache and stats did not help.

Setting the Memory limit to 1 Gigabyte for a simple file-listing operation seems a bit over the top. Is there no way to fix this in code so the script does not consume such enormous amounts?

mesoweb-wp    | [Sun Mar 07 21:27:00.834357 2021] [php7:error] [pid 83] [client 172.18.0.1:38994] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/wp-includes/meta.php on line 1078

There are also a lot of warnings that are probably unrelated but here they are nonetheless:

mesoweb-wp    | [Sun Mar 07 21:27:00.587248 2021] [php7:warn] [pid 83] [client 172.18.0.1:38994] PHP Warning:  array_keys() expects parameter 1 to be array, null given in /var/www/html/wp-content/plugins/download-manager/libs/class.AuthorDashboard.php on line 65
mesoweb-wp    | [Sun Mar 07 21:27:00.587609 2021] [php7:warn] [pid 83] [client 172.18.0.1:38994] PHP Warning:  Invalid argument supplied for foreach() in /var/www/html/wp-content/themes/mesobasic/download-manager/author-dashboard.php on line 15

• This reply was modified 4 years, 11 months ago by MESO.

PHP: 7.*

WPDM: 5.3.3

Thank You!