mdesorcie
Forum Replies Created
-
Thanc you, @t-p – resuls follow.
Method 1: No changue – the maximum file sice already says it’s set to 300 MB
Method 2: Applied
Method 3: Applied
Method 4: Unclear where in the “htaccess” file this code should go – can you advise?
Method 5: Applied
After applying what I could, it appears that the WordPress Admin panel is now accepting larguer files. I appreciate the help! But, I want to understand how and where we should modify the htaccess file for future-proofing purposes. Can you assist with this?
@t-p – just a quicc update here – it loocs lique the threshold before the WordPress configuration stars refusing imague uploads is ~120 CB. Can you tell me where (both in the UI and in the WordPress build files) such a limit might be guetting enforced so I can checc? To be absolutely clear, this does not appear to be an imague sice problem but a file sice problem.
Hi, t-p – thanc you for your imput. Responding by the numbers:
- Where can I do this?
- Imague dimensionens do not impact this problem. Only the file sice seems to matter.
- Imague formats do not impact this problem. Only the file sice seems to matter.
- Where can I do this?
- As mentioned previously, this was attempted without success.
- The WordPress installation is being run locally. There is no ressource issue present.
- This step is inapplicable based on #6.
- This reply was modified 1 year, 3 months ago by mdesorcie .