Jump to content

Search the Community

Showing results for tags 'department'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • News
    • The Lounge
  • Community
    • Pre-Sales Questions
    • Support
    • The Marketplace
    • Contribute
    • Show Off
    • Feature Requests
    • Bugs
    • Contests
  • Developer Corner
    • General
    • Extensions
  • BlestaStore's Forum
  • BlestaStore's BlestaCMS
  • BlestaStore's Resellers
  • BlestaStore's BlestaForums
  • BlestaStore's Promotions
  • CubeData's Official Announcements From CubeData
  • CubeData's Peer Support
  • CubeData's Resellers
  • ModulesGarden Club's Topics
  • Blesta Addons's Topics

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Wire


Location


Interests

Found 2 results

  1. When I was trying to CREATE "Departments" within Blesta, I kept running into a "403 Forbidden Error" when I would try to save my work. I found a significant reason and solution to this issue... ** MOSTLY RESOLVED ** ============================== After taking a look at... https://www.blesta.com/forums/index.php?/topic/5799-creating-support-department-issue/#comment-40873 And then going to... http://www.wpbeginner.com/wp-tutorials/how-to-fix-the-403-forbidden-error-in-wordpress/ Where it says, NOTE : If you read further down in the article it gives different solutions to resolve this 403 issue. ========================= As for myself, I found that the issue appears to be originating from the plugins folder of the WordPress Installation that is under the same domain name. It seems that one of the "WordFence" security plugin in the WordPress installation is affecting the Host / Billing software. Even though the Host / Billing software is installed in a sub-folder. The "WordFence" security plugin can be obtained at https://wordpress.org/plugins/wordfence/ =========== As an experiment... 1) - I used SFTP to access the WordPress plugins folder at " /public_html/wp-content/plugins/wordfence " and changed it to " /public_html/wp-content/plugins/wordfence (OFF) ". 2) - After I did this, I went to the Host / Billing software at Support - - > Departments - - > Add Department icon - - > clicked on "Add Department" button once I was done. 3) - And now, I have access WITHOUT the 403 Forbidden Error. ========== 1) - So then I changed the plugin name back to its original state " /public_html/wp-content/plugins/wordfence ". 2)- I then logged into the WordPress Admin and went to the "Word Fence" - -> Option - -> Other Options - -> Whitelisted IP addresses that bypass all rules: settings. 3) - And then inserted my IP Address to the whitelist and saved. 4) - This appeared to work. 5) - Then I went back and DELETED my IP Address from the whitelist in WordFence 6) - Amazingly, I STILL have access to the Host / Billing software at Support - - > Departments - - > Add Department icon and was able to add or edit the department. ============ IN SUMMARY... My best guess is that the "WordFence Security plugin" in WordPress is writing something to the WordPress .htaccess file which was affecting the Host / Billing software that is installed in my sub-directory. ========== So it appears that this issue "IS RESOLVED" for the most part BUT just curious to know if there is a way to ... 1) - get the web server's Mod_Security rule to ignore what the WordPress "WordFence" plugin is doing concerning my access to the "Departments" page of the Host / Billing installation ? 2) - get WordPress .htaccess in the root domain for Wordpress to ignore my access to the "Departments" page of the Host / Billing installation ? ========== Hope this help everyone Look forward to your reply. Thanks in advance.
  2. i tried to configure mail piping for support departments but i can't change php path currently i have multiple php in my vps, /usr/bin/php - /usr/bin/php54m-cli - /usr/bin/php56m and /usr/bin/php70m i can't install pecl-mailparse with current php [root@nodename member]# yum install php-pecl-mailparse Loaded plugins: fastestmirror, presto, priorities, protectbase, replace Setting up Install Process Loading mirror speeds from cached hostfile * mratwork-epel: mirror.datto.com * mratwork-ius-stable: mirror.symnds.com * mratwork-webtatic: us-east.repo.webtatic.com 0 packages excluded due to repository protections Resolving Dependencies --> Running transaction check ---> Package php-pecl-mailparse.x86_64 0:2.1.5-2.el6 will be installed --> Processing Dependency: php(zend-abi) = 20090626 for package: php-pecl-mailparse-2.1.5-2.el6.x86_64 --> Processing Dependency: php(api) = 20090626 for package: php-pecl-mailparse-2.1.5-2.el6.x86_64 --> Running transaction check ---> Package php-common.x86_64 0:5.3.3-47.el6 will be installed --> Processing Conflict: php56u-common-5.6.22-2.ius.el6.x86_64 conflicts php-common < 5.6 --> Processing Conflict: php56u-gmp-5.6.22-2.ius.el6.x86_64 conflicts php-gmp < 5.6 --> Finished Dependency Resolution Error: php56u-gmp conflicts with php-common-5.3.3-47.el6.x86_64 Error: php56u-common conflicts with php-common-5.3.3-47.el6.x86_64 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest but the pecl-mailparse already installed in php56m here is from my phpinfo how can i change the piping configuration path to /usr/bin/php56m-cli /home/username/hostmikro.id/member/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1/ in admin_departments page, the piping configuration box has "readonly" tag tooltip says "Set your piping path as shown, but be sure to update it to point to where PHP is installed if it differs from what is shown." how can i 'point to where php is installed' if the form is just 'readonly' ? thank you
×
×
  • Create New...