I'm putting together a site using Joomla 4.1, CB 2.7.2 and JA Social II. I've been following the documentation to deploy and am finding several things not looking right, and some things not working at all.

First, the Login Module will not display in content-mass-top at all. I can get it to show up if I place it in sidebar-1, but then none of the other options seem to work. I also am seeing issues with fonts.

I'm going to try the suggested fix I see in another thread regarding fonts. But I'm not sure what to do about the login section at all. Of important note, this was working when I first installed, but then stopped after a CB Build update was applied this week. I suspect CB broke something, but I'm really not sure.

Suggestions welcome. I'd love to get this working again.

    Updated with the patched file from the referenced discussion. I'm still not able to display the login module when set up as the documentation specifies (in content-mass-top).

    Looking for more ideas...

      saguaros

      SuperAdmin credentials provided. This server is behind a reverse proxy, so if you need FTP access, I will have you use a jump server for that.

          saguaros
          I reset the password and re-tested that I am able to login with the account credentials I provided. Let me know if you still have trouble getting in.

              chrisw0830 I see no code in the file: /templates/ja_social_ii/less/extras/com_comprofiler.less

              Could you update this file as I suggested above?

                ...Wow. Actually your feedback may have accidentally solved the problem for me.

                I connected via ssh to the server and was able to use less to view the contents of the file. Then it dawned on me that, if you can't see code in a file that I could at the CLI of the server itself, something else must be wrong.

                ...Like file permissions.

                So I checked, and sure enough, it seems there was a permissions problem with the template folder itself. the directory was owned by apache:apache but was apparently set to be read only. Adjusting the ownership and permissions to fit the rest of the site seems to have fixed the problem for now. I'm going to dig through it to make sure everything else is working. But we may be good to go...!

                  Write a Reply...
                  You need to Login to view replies.