JS Investa
Robert
Hi,
A few of the issues I've encountered thus far after setting up the JS Investa quickstart template.
The first issue is immediately apparent after setting up the default JS Investment quickstart configuration; which includes Joomla v4.4.0, SPPB v5.1.6, and Helix Ultimate v2.0.17. As noted in the RED CIRCLES below, when editing the template style, the Helix Ultimate menu runs off at the bottom of the screen; displaying the Advaned menu item below the Windows taskbar. Additionally, the menu and submenu items; Update Settings, Email, and License Key are being displayed as HELIX_ULTIMATE_LICENSE_UPDATE, HELIX_ULTIMATE_JOOMSHAPER_EMAIL, and HELIX_ULTIMATE_JOOMSHAPER_LICENSE_KEY instead. Updating to Helix Ultimate v2.0.18 does not fix this issue.
The next issue shown occurs upon updating to Joomla v4.4.2; also noted with RED CIRCLES below. Several Helix Ultimate menus and submenus now have similar issues, as noted above. Subsequent update to Joomla v5.0.2 does not fix this issue either.
Another issue that is encountered has to do with extension update notifications. The installed versions of Helix Ultimate (v2.0.17), SP Simple Portfolio (v2.0.7), and SP Image Gallery (v2.0.3) are noted as needing to be updated to v2.0.18, v2.0.8 and v2.0.4, respectively. Likewise, the installed version of SPPB (v5.1.6) is noted as needing to be updated to v5.2.6. Updating SPPB to v5.2.6 prior to updating the other 3 extensions cancels out the update notification of all the extensions without them actually being updated. The 3 extensions can be updated of course but someone might assume that they were updated via the SPPB update without realizing that that is not the case, since they are actually still the template's default version installs. Not sure why the SPPB v5.2.6 update is canceling out the update notification for those extensions. Not a big issue in and of itself, unless whatever is going on within the SPPB update that is triggering this behaviour also blocks/disables other extensions' update notifications as well.
One other item of note; the database items under postinstall_messages all contain the incorrect extension_id; 229, instead of 700. The Post-installation and Upgrade Messages are noted as "You have read all the messages."; even though 4 unread messages are still flagged for review. As before, attempting to Reset Messages does not fix this issue so the database items must be edited manually. This is an old issue that seems to continue being a problem to this day with some of the JS templates.
On a side note; I noticed that almost every SP database entry is set to the outdated collation utf8_general_ci instead of utf8mb4_unicode_ci or the like. Why is this still being used since utf8_general_ci has been deprecated for quite some time? Oddly, both speasyimagegallery entries are set to utf8mb4_unicode_ci.
Regards.
BOFHJunior
Accepted AnswerHey Robert, i had the same language bug issue and you can find the answer via Searching the Forum or here in my post: https://www.joomshaper.com/forum/question/30521
I saw also the 4 Post-installation and Upgrade Messages that cannot be red and cannot be deleted. But i don't want to play always Beta Tester for Joomshaper so i did not posted it here.
And then look through this Template. You will find unused menu entries for example. It has to be cleaned and reviewed.
Robert
Accepted AnswerHi BOFHJunior,
Was a bit confused by your first paragraph but after relooking through your forum post, I downloaded/uploaded that fix posted by Paul and it fixed that issue. A new quickstart file should have been created with that language file fix added. Would save a lot of wasted forum posts. :-/ Thanks.
As for your second paragraph, I actually provided the answer to fix that particular database issue. I posted the fix on purpose for anyone else reading my post who wanted to fix it themselves.
And finally, your third paragraph. I've no concern about menu items since that is something that I modify as necessary anyway, so that is a nonissue.
Regards.
BOFHJunior
Accepted AnswerHey Robert, i am glad that i could help. Yes, normally it is the to do of the Support to inform you but they are massively understaffed. I posted already in another post that with every Hugh feature like Easy Store they have to increase the staff... Yes, a new QuickStart has to be uploaded that fixes this annoying issue!
I know you provided it to help, but i wanted to publish my frustration, maybe the CEO reads it (probably not) and want to improve the situation.
Ofi Khan
Accepted AnswerHello Robert
Apology for the delayed response. I hope that all your issues are solved by now. Which database entries are you talking about? Is it for Investa template? On investa, I see unicode collation.
Post installation message error has been addressed. It will be fixed soon. Thanks for your feedback on this.
Best regards
Robert
Accepted AnswerHi,
This entire forum post relates to JS Investa; hence the title. Below is a snapshot of the default database created by the JS Investa quickstart template. I have looked at other databases that were either JS templates or other developers' templates that use SPPB; they all have the same database collations. Not sure what you're accessing for a comparison but the image below is from the database created from the current quickstart installation file downloaded from Joomshaper; without any edits whatsoever, using a clean database set to the utf8mb4_unicode_ci collation. As stated previously, both SP Easy Image Gallery DB entries are set to utf8mb4_unicode_ci but every other SP database entry is set to the outdated collation utf8_general_ci.
As for the Helix Ultimate issue; yes, that is fixed now. So, either a new quickstart file should be created with that language file fix already implemented and uploaded to the Joomshaper download site or the file that Paul posted should be added to the template's download section on Joomshaper with an info file explanation, since this issue has been noted previously by others. Searching the forums for the fix isn't feasible since the underlying problem is not necessarily obvious.
Addendum
For an experiment, I downloaded and completed a clean Joomla! Full Installation of v5.0.2 into a likewise clean database, which was configured with the utf8mb4_unicode_ci collation. Upon completion of the CMS installation, I checked the database again and every database entry still reflected the database's default collation. I then added the SPPB v5.2.6 extension and rechecked the database. Same as shown in the picture above from the JS Investa database snapshot, all of the SP entries added to this clean database were set to the outdated collation utf8_general_ci as well. The entirety of the other database entries are still set to the original database's utf8mb4_unicode_ci collation.
Regards.
Ofi Khan
Accepted AnswerI have checked it here:
installation/sql/mysql/base.sql
This is the collation: utf8mb4_unicode_ci
You can download the quickstart now and check.
Robert
Accepted AnswerHi,
Don't know what to tell you but I just did another clean installation of the JS Investa template quickstart, without any difference. I did verify that the base.sql file does indeed state to set utf8mb4_unicode_ci collation but the SP DB entries; as stated above, are not conforming to that. Something else is issuing the command to set those entries to utf8_general_ci collation. I did find that if I update the DB manually to the utf8mb4_unicode_ci collation and then update the installed version of SPPB (v5.1.6) to the latest version, the SP DB entries noted above then remain set to the utf8mb4_unicode_ci collation. No idea what the issue is but that's for your Dev team to figure out.
Regards.