Marco Junior

No, as I mentioned I did a clean install. After the installation was complete I took the backup data from the first installation, since the data is my game guides. So I sent this data to the table and then this error appeared. Since then it has never gone away!

Any solution for me problem ?

I believe that this does not resolve my problem, because I reinstall full IC5 and this appear on the page.

Clear install !

It would be great if the IC team could decide once and for all who will be able to use the subscribed topic feature. I really appreciate this feature and it is definitely a feature that every community needs to have. I would love to test this in my community, it was one of the features that made me renew my license, and make myself available for the IC5 trial period! Please give us a position regarding this, my members ask me about this feature all the time.

@Daniel F Yeah 😄 Thanks for this work fine now.

So if I create specific classes and define them there, the classes will load without problems? I had tested this in the past and for some reason it didn't work. I'll try again!

On current version the column prefix for groups have value : varchar 250 but this is small value for us to define colors and personalization in our groups. Through this I suggest changing it to a value greater than or equal to 500. In this value I was able to define my groups without any problems. However, the support tab will alert me that there is a problem in my database, due to the change in the value of this column. I use it this way, but to use it this way it was necessary to change the column value as mentioned above. However, the support page keeps alerting me about this change and that is not good. The idea is to increase this value or somehow remove the information that this is a problem.

if your reply is direction for me. <?php exit; ?> Tue, 19 Nov 2024 00:04:51 +0000 OutOfRangeException::0 #0 /home/lightningmu/public_html/community/applications/blog/sources/Entry/Entry.php(1030): IPS\Patterns\ActiveRecord::load(8) #1 /home/lightningmu/public_html/community/static/templates/blog_front_browse.php(1364): IPS\blog\Entry->category() #2 /home/lightningmu/public_html/community/system/Theme/SandboxedTemplate.php(68): IPS\Theme\class_blog_front_browse->indexGridEntry(Object(IPS\blog\Entry), true) #3 /home/lightningmu/public_html/community/static/templates/blog_front_browse.php(1022): IPS\Theme\SandboxedTemplate->__call('indexGridEntry', Array) #4 /home/lightningmu/public_html/community/system/Theme/SandboxedTemplate.php(68): IPS\Theme\class_blog_front_browse->indexGrid(Object(IPS\Patterns\ActiveRecordIterator), Array, Array, Array, 'grid', NULL) #5 /home/lightningmu/public_html/community/applications/blog/modules/front/blogs/browse.php(131): IPS\Theme\SandboxedTemplate->__call('indexGrid', Array) #6 /home/lightningmu/public_html/community/system/Dispatcher/Controller.php(139): IPS\blog\modules\front\blogs\browse->manage() #7 /home/lightningmu/public_html/community/system/Dispatcher/Dispatcher.php(169): IPS\Dispatcher\Controller->execute() #8 /home/lightningmu/public_html/community/index.php(16): IPS\Dispatcher->run() #9 {main}

Is there a way to remove this? This error is disturbing lol my eyes scream when I see it. I noticed that after applying the update it is still there.

The font change option is removed on BETA:5 ?

This is bad, 😕 but I will wait !

Yes, I realized that you were not interpreting me correctly. The word "Fixed" made it clear that I wanted a correction, but I was not specifying where or why. Anyway, thank you for all your attention and patience! I hope they can understand = ) It's not something serious, but it is a bit annoying.

This is my answer, maybe you didn't understand. Shouldn't the position be "FIXED"? Because when the profile element is loaded the footer is moving creating a large space where it shouldn't have this behavior, keeping it "FIXED" just making the element/box of the profile demo content have a higher z-index would already be a solution. You can see this 🙂 Desktop 2024.11.18 - 08.25.37.02.mp4

I don't know if this is related to template errors. If so, I would like to add that even without any type of change in themes I am also receiving template error messages. Please note that: In the support tab, as mentioned in some topics, there are no irregularities or problems in my environment, there is no error message or anything else that could say or explain why the messages about template problems are appearing. A very important point: after seeing these messages, I ended up getting scared and then decided to do a new installation, without any chance of restoring previous files or data so that there would be no possibility of these errors bothering me again. And guess what? Errors appeared in blog content after a completely new installation.