I am so pleased to announce you that Masino Extensions for PHPMaker 12 are just released today. It took about one and a half weeks for me to upgrade all of my extensions that I made for PHPMaker 11 so that they will work properly for PHPMaker 12, too.
There are 15 (Fifteen) extensions now available for PHPMaker 12. So here they are:
- MasinoCustomCSS12
- MasinoCAPTCHA12
- MasinoLogin12
- MasinoForgotPwd12
- MasinoRegister12
- MasinoChangePwd12
- MasinoHorizontalVertical12
- MasinoHeaderFooter12
- MasinoFixedWidthSite12
- MasinoDetectChanges12
- MasinoPreviewRow12
- MasinoVisitorStatistics12
- MasinoLoadingStatus12
- MasinoSearchPanelStatus12
- MasinoAutoNumeric12
Please note that there are also some new language phrases were added into the XML Language Files in C:\Program Files\PHPMaker 12\languages folder. So make sure you have already updated your XML Language Files in the PHPMaker installation folder with the modified ones below before generating ALL the script files using Masino Extensions for PHPMaker 12.
Important to know, since v12.0.6, the phrase id "NoPermission" had been modified. Therefore, you need implement this update including the customization I made in the XML Language Files.
I attached the modified language files (English, Indonesian, and Arabic), so that you don't need to update or insert the new phrases into your XML Language Files. You may simply download the XML Language Files from this link. Make sure you download only the files/extensions that related to PHPMaker 12.
Now you can also download Masino Extensions from this link
As always, extract the extensions to your C:\Program Files\PHPMaker 12\extensions folder, afterwards enable all of them from Tools -> Extensions of your PHPMaker application. Also, extract the .xml language files into your C:\Program Files\PHPMaker 12\languages folder.
Donโt forget to play with some of their Advanced settings in order to see some new settings available.
You can also see the Demo of web application that generated by PHPMaker 12 which uses those Extensions above from this post. You can use the same account for login to the demo site; as well as for version 11.0.6 (the latest stable version for PHPMaker 11).
Enjoy! ๐
Masino
Do we need to make any changes to our projects to remove anything from the v11 extensions?
Since Masino Extensions v11 are not compatible anymore with PHPMaker v12, then you need to remove them from the project.
PHPMaker: Generate ewconfig page error
PHPMaker (ewExewconfig): Microsoft JScript runtime
error (1A8), line 11, column 1
Description: Object required
This error will be happened if you do not enable all of Masino Extensions. Please enable all of Masino Extensions for v12, and then regenerate all the script files again.
For more information, please read Important Things about Masino Extensions.
When is PHPMaker 12 project files released?
I will release it tomorrow. Please come back again tomorrow (August 4, 2015).
I have
Notice: Use of undefined constant MS_SHOW_HELP_ONLINE – assumed ‘MS_SHOW_HELP_ONLINE’ in C:\xampp\htdocs\footer.php on line 88
on every page when I use “MasinoHeaderFooter12” What am I missing?
Make sure you have already enabled all Masino Extensions. Please read this article for more information: Important Things about Masino Extensions.
I keep getting the error below when I generate my project. At first I thought maybe I didn’t enable some of the extension. After I turned on all extensions, the error still occurred. Check and uncheck that EnablePermissionsForExportData in FixedWidth extension doesn’t make any difference.
PHPMaker: Generate Table add page error.
PHPMaker (ewExadd): Microsoft JScript runtime error (1391), line 3977, column 1.
Description: ‘bEnablePermissionsForExportData’ is undefined.
There is no issue with EnablePermissionsForExportData setting on our side. Therefore, please double check and make sure all of Masino Extensions have been enabled properly.
If the issue remains, remove the template cache from Tools -> Delete Template Cache and regenerate all the script files again.
Ok.. To proof that there is nothing wrong with my project, I created a brand new project using the phpmakerdemo database. I’ve also deleted the template cache. Only 3 tables selected: employees, userlevels and userlevelpermissions..
I then proceed to setup the standard security settings in PHPMaker by defining the tables and fields for Users, UserLevels and User Level Permissions.
Next I enable all the Masino extension, using the default setting, without configuring anything.
Once I clicked Generate, it will come out the same error. If I disable the MasinoFixedWidthSite v12.0.2 extension, there is no error. I’ve even redownloaded the extension to make sure I have the latest version. I’m also running PHPMaker v12.0.2
I’ve no idea what’s went wrong with the MasinoFixedWidthSite extension.
Could you please to try generate the demo project that I provided on this site, too? Have you seen the same error? Please let me know.
I got the demo project working fine.
After tinkering a bit with the settings, I found out that MasinoFixedWidthSite extension will only work if you go to PHPmaker PHP -> Page Options (Global) tab and check either on the “Enable export in list page” or “Enable export in view page”.. Seems like the variable “bEnablePermissionsForExportData” is dependent on that option.
Thanks for the feedback.
Yes, actually if export data is not enabled either from that Page Options (Global) or from Table tab, then it will raise an error.
The option will cause the permissions for export data should be included in the generated script files.
Please download again MasinoFixedWidthSite12 extension. I just updated it today, August 29, 2015, so that the option will not depend on export setting that belongs to PHPMaker.
Below are the screenshot of the extension that I enabled:
http://i.imgur.com/x3i1SEF.png
http://i.imgur.com/Iyw80E1.png
Thanks.
Masino, I have another challenge for you. Have you ever thought about adding a “Hints and Tips” popup when entering a site? You could modify the authorized users table for a flag to allow them an option of viewing future popups or not. The content would be derived from a new table in the database.
What do you think?
Keith, thanks, and that’s a good idea. Yeah, I used to implement it in the desktop applications using VB6. Let’s see whether I could do the similar thing in PHPMaker.
If not too much trouble, could you make a v11 as well? I’m still in the process of converting my projects.
I will try the best I can, but I am really sorry I cannot promise you about the time it will be released.
NO problem. Thanks for all you do!!!
There’s a custom view to preview Youtube video as such. Is Masino extension capable of viewing/preview user uploaded videos on local server or what do you think would be the best way of implement video viewing?
At the moment no. Masino Extensions is not capable of viewing/preview user uploaded videos. Please use the custom view that provided by PHPMaker.
If I set TableWidthStyle = 1, it looks nice for my desktop but it makes my mobile layout fixed width too and not 100%. Any way to not apply this setting to mobile layout?
The Footer doesn’t adjusted to the same width when I set TableWidthStyle=1 in MasinoFixedWidth in Advanced properties. That makes the layout kind of weird. Only the header does but not the footer. FYI, I’m also using MasinoHeaderFooter extension.
Yes, thanks for the feedback. Will fix it in future version.
At the moment, please use either Auto or 100% style.
Please download again MasinoFixedWidthSite12 and MasinoHeaderFooter12 extensions that I just updated today on September 2, 2015.
Now the footer width will automatically be adjusted when we set TableWidthStyle=1. This update also fix the issue of wrong total width site when we use the left/vertical menu.
Make sure you have already regenerated ALL the script files; not only in Other files section; but for ALL the script files, since the List pages also need to be regenerated.
Thanks for the update!
Please have a look at the demo project that I provided on this site. There are another two table width style; 100% and Auto. For mobile version, you should use those another both styles. The fixed style is useful to be used in desktop mode.
Thank you. I will try it out. Just that I like the fixed style on my desktop but at the same time, I’ll like my project to be mobile-friendly. Maybe some enhancement about using the fixed style but not applicable to mobile layout can be done in the future. Meanwhile, I’ll try the other options. Thanks again.
Thanks for the feedback. Let’s see whether I could implement it for the future version.
Any idea why CAPTCHA for “Change Password” page can’t work? I have no problem with CAPTCHA at login page. Below is the error:
http://i.imgur.com/r2BuePb.png?1
I’ve enabled Change Password and CAPTCHA in the Advanced Security -> User Login Options. MasinoCAPTCHA also already enabled. I only enable CAPTCHA for login and change password page. I’ve no idea else that I need to set. I’ve tested your test project and it is working but not mine.
Looking at the changepwd.php script, I saw the following code generated:
http://i.imgur.com/oYWMFVw.png?1
Could you please compare and tell us about the different settings between yours and the demo project?
Also, could you please adjust your setting and make it same as the demo project? Let us know whether this would help.
Please ignore this my comment above.
Well, I think I just found out the cause of this issue and fix it. Apologies for this inconvenience.
Please download again MasinoChangePwd12 extension that I just updated today on September 3, 2015.
Thank you. Tested ok!
You’re welcome.
Masino,
I would like to suggest an enhancement to your extensions.
When a user changes a password, the new password is sent via plain text. I think that is a real violation of good security practices. Perhaps you could add a feature to continue to allow this or perhaps replace it with some text that indicates the password has been changed or replace the password with all “*”. Whatever works best for you. I prefer the replacement of the password line in the txt file with text explaining the new password was changed.
Up to you.
Good idea. Thanks for your suggestion. Will add a new option, so that we can decide whether to send the password in plain text or in ********* format.
I just added a new option ShowPlainTextPassword which is False by default into MasinoChangePwd12 extension. Please download it again.
THANKS!
You’re welcome.
Hi Masino, Just a suggestion, it would be great if login page or anything to do with credential to have the input box to have the parameter -> autocomplete=off.
Thanks for the suggestion, but I think this feature is a browser built-in one.
I’m integrating PHP Report Maker with my PHPMaker. Everything works fine except the MasinoLoadingStatus12. When I clicked to export to Printer Friendly format, the loading status icon (I choose center-radar) will keep spinning for a minute before it stopped by itself.
Basically, the extension will detect the last elemen in the footer of page loaded then it will stop running by itself.
Found abug for MasinoFixedWidthSite12 or MasinoHeaderFooter12.
This only happens when I set ShowEntireHeader = False in MasinoHeaderFooter12 and TableWidthStyle=1 in MasinoFixedWidthSite12
Header looks ok upon first load
http://i.imgur.com/ttoNaAM.png
If I try to scroll down, the header expanded.
http://i.imgur.com/t8xb3ac.png
Thanks for reporting.
Please download again MasinoHeaderFooter12 and MasinoFixedWidthSite12 extensions that I just updated today, November 2, 2015.
I noticed there’s a new variable in the template_2.php and it causes error in the login page generated. It shows empty white screen and view source shows the following error:
var EW_IS_AUTOLOGIN =
Fatal error: Call to undefined function IsAutoLogin() in E:\xampp\htdocs\KIOSKCMS\header.php on line 114
I’ve also already upgraded my phpmaker from 12.0.2 to 12.0.3 and updated all the extensions.
There is no issue regarding IsAutoLogin() function in our side. Everything runs properly.
Make sure you have already uninstalled v12.0.2 completely before installing v12.0.3.
Make sure also you have already regenerated ALL the script files, especially ewshared12.php, since the function above should be located at the bottom line of inside this file.
Hmm.. Happened a few times to my project file especially when I upgraded to a new version. Had issues generating the script due to some error in ewAdd or something… Had to remove all the extensions that I use.. Generate the script.. Then use back the Masino extension..
Try remove the old template cache from Tools -> Delete Template Cache of your PHPMaker project, afterwards regenerate ALL the script files again.
It is working fine now after I do the steps I mentioned about. Thank you!
You’re welcome.