I Love PHPMaker

... because it gets even more powerful and flexible!!

I Love PHPMaker » PHPMaker Extensions » Masino Extensions for PHPMaker 12 Is Released!

Masino Extensions for PHPMaker 12 Is Released!

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:

  1. MasinoCustomCSS12
  2. MasinoCAPTCHA12
  3. MasinoLogin12
  4. MasinoForgotPwd12
  5. MasinoRegister12
  6. MasinoChangePwd12
  7. MasinoHorizontalVertical12
  8. MasinoHeaderFooter12
  9. MasinoFixedWidthSite12
  10. MasinoDetectChanges12
  11. MasinoPreviewRow12
  12. MasinoVisitorStatistics12
  13. MasinoLoadingStatus12
  14. MasinoSearchPanelStatus12
  15. 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! 🙂

Comments

  2. PHPMaker: Generate ewconfig page error
    PHPMaker (ewExewconfig): Microsoft JScript runtime
    error (1A8), line 11, column 1
    Description: Object required

  4. 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?

  5. 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.

        • 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.

  6. 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?

  7. 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?

    • 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.

    • 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.

  9. 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.

  10. 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.

  12. 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.

  14. 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

Leave a Reply

Recent Comments

Demo Website

Another Demo

The following template are not available in this site (must be purchased separately)

Demo Explanation

The fourth demo link is the example to show you how we can force users to select Province and to enter the search keyword (at least 3 characters) before search for data. The Advanced Search will show you how to force users to select at least Province, Regency, and Subdistrict before search for data.

Categories

Articles based on version