Answers.Body: <p>Finally solved this.
  There was an .htaccess file in the wp-content/uploads/civicrm folder blocking all (direct) access to files in this directory. added below.
  Don't know how it got there - presume another extension?</p>
  <p>content of file:</p>
  <p>&quot;&lt;Files &quot;*&quot;&gt;</p>
  <h1>OpenLiteSpeed 1.4.38+</h1>
  <p>&lt;IfModule !authz_core_module&gt;
  RewriteRule .* - [F,L]
  </p>
  <h1>Apache 2.2</h1>
  <p>&lt;IfModule !authz_core_module&gt;
  Order allow,deny
  Deny from all
  </p>
  <h1>Apache 2.4+</h1>
    
      Require all denied
    
  
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-07-18T07:50:04.240Z
Answers.LastActivityDate: 2023-07-18T07:50:04.240Z
Answers.UserDisplayName: LesleyJill
Answers.Body: <p>You say you have a 404 error, so:</p>
  <ul>
  <li>Is the file on the server where it's supposed to be?</li>
  <li>Have you checked both the file <em>permissions</em> and <em>ownership</em>? Are they correct?</li>
  </ul>
  <p>After that, you're getting into some weird scenarios, like web server misconfiguration.  It may be worth looking at the HTTP response headers to see whether the 404 is coming from WordPress or the web server.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-06-28T20:46:51.147Z
Answers.Text: The fact that you're seeing this problem even when you revert strongly suggests a file permission/ownership issue.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-06-28T20:29:45.257Z
Answers.LastActivityDate: 2023-06-28T20:29:45.257Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>WP 6.2 civi 5.61.1 or 5.61.4 or 5.62.2 formcore 5.62.1
  After upgrade to mosaico 2.12 could not edit existing templates. Console 404 errors.
  I tried: installing &amp; uninstalling, changing resource url to absolute, asset cache on, off, auto, making ext directory 777, uninstalling civigrant</p>
  <p>Now upgraded to civi 5.62.2 and mosaico 3.1.1687383640.
  Mosaico page and &quot;new template&quot; page images below. Selecting new template just hangs with &quot;loading&quot;</p>
  <p>Civi log shows:
  Jun 27 15:37:40  [error] Afform error: cannot process ~/afsearchMosaicoTemplateList/afsearchMosaicoTemplateList.aff.html: malformed entity name ()</p>
  <p>Browser console has 404 for https://website/wp-content/uploads/civicrm/ext/uk.co.vedaconsulting.mosaico-2.8/css/mosaico-bootstrap.css?r=0uwJ4en_US</p>
  <p>full console error below</p>
  <p>At wit's end really &amp; boss wants newletter out yesterday!</p>
  <p><a href="https://i.sstatic.net/1kPpF.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/1kPpF.png" alt="enter image description here" /></a>
  <a href="https://i.sstatic.net/zTaYE.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/zTaYE.png" alt="enter image description here" /></a>
  [![enter image description here][3]][3]</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-06-28T07:25:10.350Z
Comments.Text: You say you upgraded to Mosaico 3.1 but your errors show 2.8 in the path.  Do you have both 2.8 & 3.1 files installed?  I'd (save and) remove 2.8 files.
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-06-28T20:00:56.587Z
Comments.Text: Yes I reverted to 2.8 in desperation. Don't have both installed.. errors are 404 in any version
Comments.UserDisplayName: LesleyJill
Tags: <mosaico>
Title: Mosaico can't create template or see existing templates
ThreadText: # Mosaico can't create template or see existing templates
  
  (Asked by: username_0 on 2023-06-27)
  
  WP 6.2 civi 5.61.1 or 5.61.4 or 5.62.2 formcore 5.62.1
  After upgrade to mosaico 2.12 could not edit existing templates. Console 404 errors.
  I tried: installing & uninstalling, changing resource url to absolute, asset cache on, off, auto, making ext directory 777, uninstalling civigrant
  
  Now upgraded to civi 5.62.2 and mosaico 3.1.1687383640.
  Mosaico page and "new template" page images below. Selecting new template just hangs with "loading"
  
  Civi log shows:
  Jun 27 15:37:40 [error] Afform error: cannot process ~/afsearchMosaicoTemplateList/afsearchMosaicoTemplateList.aff.html: malformed entity name ()
  
  Browser console has 404 for https://website/wp-content/uploads/civicrm/ext/uk.co.vedaconsulting.mosaico-2.8/css/mosaico-bootstrap.css?r=0uwJ4en\_US
  
  full console error below
  
  At wit's end really & boss wants newletter out yesterday!
  
  [![enter image description here](https://i.sstatic.net/1kPpF.png)](https://i.sstatic.net/1kPpF.png)
  [![enter image description here](https://i.sstatic.net/zTaYE.png)](https://i.sstatic.net/zTaYE.png)
  [![enter image description here][3]][3]
  
  **Tags:** mosaico
  
  > **Comments:**
  > **username_1**: You say you upgraded to Mosaico 3.1 but your errors show 2.8 in the path.  Do you have both 2.8 & 3.1 files installed?  I'd (save and) remove 2.8 files.  
  > **username_0**: Yes I reverted to 2.8 in desperation. Don't have both installed.. errors are 404 in any version  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2023-07-18. Score: 1
  
  Finally solved this.
  There was an .htaccess file in the wp-content/uploads/civicrm folder blocking all (direct) access to files in this directory. added below.
  Don't know how it got there - presume another extension?
  
  content of file:
  
  "<Files "\*">
  
  # OpenLiteSpeed 1.4.38+
  
  <IfModule !authz\_core\_module>
  RewriteRule .\* - [F,L]
  
  # Apache 2.2
  
  <IfModule !authz\_core\_module>
  Order allow,deny
  Deny from all
  
  # Apache 2.4+
  
  Require all denied
  
  
  ---
  
  ### Answer by username_2 on 2023-06-28. Score: 0
  
  You say you have a 404 error, so:
  
  * Is the file on the server where it's supposed to be?
  * Have you checked both the file *permissions* and *ownership*? Are they correct?
  
  After that, you're getting into some weird scenarios, like web server misconfiguration. It may be worth looking at the HTTP response headers to see whether the 404 is coming from WordPress or the web server.
  
  > **Comments:**
  > **username_2**: The fact that you're seeing this problem even when you revert strongly suggests a file permission/ownership issue.  
  
  ---
  
  