Facing some issue while migrating to the production stage on server

[AFA]

Hello team, 

Can anybody help me with this? We are facing the some issues while moving to the production stage.

1. These two pluslets are not working in the "Subject Specialist, AND Expert" pluslet box. When we drag and drop into the guide then nothing is visible. All pluslet box is working fine except these two. This pluslet is working fine "Subject Specialists" not the two above mention is not working.

2. The stats page is showing blank (BASEURL/control/guides/stats.php)

3. In the databases.php, When I enter any term in the search box the result is not showing, but while tying the search term the autocomplete suggestion is working fine.

I follow these steps to migrate/restore to SubjectsPlus 4.6 on the university server.
I am not following the installation process. I just paste the folder in the server directory restore the database and then adjust the configuration in the config.php file.

https://apply.jgu.edu.in/sp/ 

[charlesbr...@gmail.com]

Hello,

I'm sorry to hear that you're facing issues while moving to the production stage with SubjectsPlus 4.6. To assist you further, I'll need some additional information from the Apache logs. Here's how we can proceed:

Pluslets Not Working:
To investigate the issue with the "Subject Specialist, AND Expert" pluslet box, we'll need to check the Apache error logs. Please provide any error messages or logs related to these pluslets. This will help us pinpoint the exact problem. Also, are there any errors in the DevTools console?

Blank Stats Page:
For the blank stats page issue, we'll also require Apache error logs. Please check for any error messages in the logs related to the URL BASEURL/control/guides/stats.php. This will give us insights into what's causing the blank page. In addition, the stats gathered are not really accurate. It is best to use google analytics.

Search Result Issue:
Regarding the search result problem in databases.php, we need to examine the Apache logs as well. Please share any relevant error messages from the logs. Additionally, if there are any specific error messages or issues that users encounter when trying to search, please describe them in detail.

To locate the Apache logs, you can typically find them in the /var/log/apache2/ directory on your server. Look for files named error.log or similar.

Once you've gathered this information, please provide it, and we'll be better equipped to diagnose and resolve the issues you're experiencing. If you have any questions or need assistance with locating the logs, feel free to ask.

Going forward we are releasing SubjectsPlus 5. It is completely rewritten using Symfony, React, and API-Platform. You can follow the development process on Github at: https://github.com/subjectsplus/SubjectsPlus/wiki/SP5-Development-Updates

Thank you for your cooperation, and we'll work together to get these issues resolved.

Best regards,

Charles

[AFA]

Dear Charles,

I have attached the error log file.

The search issue, what I noticed is that in the theme-based databases.php, there is no such layout code block that displays the search result on the databases.php page like that in index.php, there is the layout of the search result display, but I examined the databases.php, there are no such things that display the result based on the search term. 

Even in every theme of databases.php such layout of the search result display

Thanks,

[charlesbr...@gmail.com]

Hello,

According to the logs you are experiencing a problem with a mysql setting.
If you have MySQL 5.7 you must disable ONLY_FULL_GROUP_BY permanently. Please refer to this stack overflow issue.
https://stackoverflow.com/questions/23921117/disable-only-full-group-by

Thanks,

Charles

[Abid Fakhre Alam]

Hello Charles,

Thank you for your reply, 

We are transferring Subjectsplus to the university server, on this server there are other things hosted, and we have hosted around more than ten services, and there is only one central MYSQL On that, there are more than ten databases on the MYSQL. So, if we disable the  ONLY_FULL_GROUP_BY permanently it might affect the other database in MYSQL. Is there any other way we can solve this problem? 

Thanks and Best Regards,

Abid Fakhre Alam

--
You received this message because you are subscribed to a topic in the Google Groups "SubjectsPlus" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subjectsplus/E0D_8MCW1Zk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subjectsplus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subjectsplus/1f71f77f-315a-480f-b8e8-e8bfd0058274n%40googlegroups.com.