Jump to content

tcnet

Members
  • Posts

    86
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by tcnet

  1. You will see "PHP notices" if you run your ProcessWire in debug mode. Please read the description for the debug mode. The debug mode is not intended for productive usage. Please turn off debug mode and you will see that everything works fine.
  2. Yes, the Debug Mode Tools-Panel is available. Please see the 3rd arrow in the last screenshot. But not all debug information seems to be available. I cannot see any PDO-Query or AutoLoad. Sorry.
  3. What's new in ProcessWire 3.0.163? See: https://weekly.pw/issue/324/ I created this module before ProcessWire 3.0.163. I thought it's time to publish it. If it is not desirable, I remove it again. Just tell me.
  4. This module for ProcessWire enables the debug mode to bypass the restriction to install modules. This is useful if you are tired to manually set the debug mode in the configuration. Note Please note that this module doesn't replace the real debug mode in the configuration file /site/config.php. With this module you will not receive any errors/notices/warnings like in the real debug mode. It serves only to bypass the restriction to install modules. Installation To install this module you have to enable the real debug mode. After installation you should deactivate debug mode again. To enable the real debug mode, download /site/config.php via FTP and open it in a text editor. Look for a line where you can find $config->debug = false; change it to $config->debug = true; save the file and upload it again. After module installation change it back to $config->debug = false;. For all future module installations, you just have to enable the debug mode in the module settings like described below. After module installation, you should deactivate it in the same way. Settings The settings for this module are located in the menu Modules=>Configure=>DebugModeSwitch. Enable or deactivate debug mode Set the checkmark (1) and click the submit button (2) will enable the debug mode (3). The debug mode can be also restricted for superusers only (4). Links ProcessWire module directory: https://processwire.com/modules/debug-mode-switch/ Github: https://github.com/techcnet/DebugModeSwitch
  5. The link doesn't work because the site-profile is still waiting for approval. Please note that a thread in this forum here is required to submit a new module or site-profile. Please be patient a few days. Thank you!
  6. This site profile for ProcessWire offers a simple, multilingual and responsive blog which doesn't require any module. It works exclusively with some template files. See: https://processwire.com/modules/site-simple-blog-multilanguage/ Installation This site profile is intended for use with a new installation of ProcessWire. Download ProcessWire, extract all files and folders and upload it into your web server folder. Download the site profile, extract the simple-blog-multilanguage folder and upload it into the same folder. Start the installation. When prompted for Site Installation Profile select Simple and Multilingual Blog Profile for ProcessWire 3x and continue with installation.
  7. Please show me an example where your dump() function returns the output. I got it only to work with echoing the output which is not what I want.
  8. Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu. The following conditions must be met for the module to work properly: Session files Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions. Serialize handler In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer. Session data The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer. Links ProcessWire module directory github.com
  9. If you exchanged the module file then the exception will occurring in a different line ynd you will not get the same error message. If you deleted table process_pageviewstat_main and installed version 1.1.1 then process_pageviewstat_main will recreated with column usr. But in this case you will not get the same error message. I guess you loading your pages from the browser cache.
  10. Did you replaced the file or not? What's the error message after you replaced the file? How you cleaned the database? Did you deleted the table process_pageviewstat_main in the database or not? Did you followed my instruction: Please delete ProcessPageViewStat and rename .ProcessPageViewStat to ProcessPageViewStat. Then execute the upgrade again. If you get the error again then delete ProcessPageViewStat and rename .ProcessPageViewStat to ProcessPageViewStat and uninstall the module from then module page and install it again.
  11. Did solved the problem? You can also replace the module file in the attachment of this message. It encloses the database execution in line 376 with a try-catch. So you are able to click the refresh button without error message. The refresh button should call the upgrade funtion or something is wrong in your PW. ProcessPageViewStat.module
  12. Or you have to add a new int column to process_pageviewstat_main named usr. This is what the upgrade function does.
  13. When you deleted the .ProcessPageViewStat already, you have to delete process_pageviewstat_main in the database before you install it again.
  14. Ok, I see the problem. Please delete ProcessPageViewStat and rename .ProcessPageViewStat to ProcessPageViewStat. Then execute the upgrade again. If you get the error again then delete ProcessPageViewStat and rename .ProcessPageViewStat to ProcessPageViewStat and uninstall the module from then module page and install it again.
  15. Press the Refresh button before you install it again.
  16. "removed module from database" How did you do that? Just deleted the tables? You will get the same error! You have to uninstall it if you want to install it from the scratch!
  17. Seems that ___upgrade($fromVersion, $toVersion) don't get called. You can use the old version. Just rename .ProcessPageViewStat to ProcessPageViewStat
  18. If you realy clicked "Upgrade" then ___upgrade($fromVersion, $toVersion) have been fired and you would not have problems. Exists a directory named .ProcessPageViewStat in the module directory? Please note the dot before the module name. If not rename the module to .ProcessPageViewStat then go to the module page, rename it back to ProcessPageViewStat and then click Refresh.
  19. This happened because you didn't realy upgrade it. You just replaced the files. In this case function ___upgrade($fromVersion, $toVersion) will be never called! Click on Modules and then on Refresh in the top right corner. This will fire the ___upgrade function.
  20. No, I haven't forgotten. The module is still under review. After approval I'll post all links.
  21. This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist. Settings The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier. Notification email Specifies the email address to which the notification emails should be sent. Email subject Specifies the subject line for the notification email. Post variables Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass Server variables Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT Link to ProcessWire module directory: https://processwire.com/modules/login-fail-notifier/ Link to github.com: https://github.com/techcnet/LoginFailNotifier
  22. This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages. Create an account Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code. Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all. Open the module settings The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.
  23. I've the filemanager.php completely rewritten. Version 1.0.3 is now available. Please make sure that the module is installed correctly.
  24. Please have a look: This is not a proper directory name for a module. Please uninstall and reinstall the module by using the "Add Module from Directory" function.
×
×
  • Create New...