Home Forums Weaver and Plugin Interaction PaymentSense Gateway Plugin – Weaver xtreme

This topic contains 8 replies, has 4 voices, and was last updated by  orbitcreative 5 months, 2 weeks ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #59291

    orbitcreative
    Participant

    I posted this in the wrong section yesterday, so my apologies in advance.

    I am trying to get the ‘PaymentSense’ plugin to work in conjunction with WooCommerce and the problem we have is that the settings page to integrate the payment gateway is blank. This plugin does work with the 2019 theme.

    When i run a de-bug, the following script appears.

    Any thoughts and ideas would be gratefully appreciated.

    <b>Notice</b>: Constant WEAVERX_VERSION already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>23</b>

    <b>Notice</b>: Constant WEAVERX_VERSION_ID already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>24</b>

    <b>Notice</b>: Constant WEAVERX_THEMENAME already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>25</b>

    <b>Notice</b>: Constant WEAVERX_SETTINGS_VERSION already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>26</b>

    <b>Notice</b>: Constant WEAVERX_THEMEVERSION already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>27</b>

    <b>Notice</b>: Constant WEAVERX_MIN_WPVERSION already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>28</b>

    <b>Notice</b>: Constant WVRX_PAGEBUILDERS already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>29</b>

    <b>Notice</b>: Constant WEAVERX_LEVEL_BEGINNER already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>31</b>

    <b>Notice</b>: Constant WEAVERX_LEVEL_INTERMEDIATE already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>32</b>

    <b>Notice</b>: Constant WEAVERX_LEVEL_ADVANCED already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>33</b>

    <b>Notice</b>: Constant WEAVERX_THEME_WIDTH already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>35</b>

    <b>Notice</b>: Constant WEAVERX_DEV_MODE already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>37</b>

    <b>Notice</b>: Constant WEAVERX_PHP_MEMORY_LIMIT already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>38</b>

    <b>Notice</b>: Constant WEAVERX_DEFAULT_THEME_FILE already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>43</b>

    <b>Notice</b>: Constant WEAVERX_DEFAULT_THEME already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>46</b>

    <b>Notice</b>: Constant WEAVERX_GOOGLE_FONTS_URL already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>51</b>

    <b>Notice</b>: Constant WEAVERX_GOOGLE_FONTS already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>53</b>

    <b>Notice</b>: Constant WEAVER_CUSTOMIZER_TYPE already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>71</b>

    <b>Notice</b>: Constant WEAVER_SUBTHEMES_DIR already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>72</b>

    <b>Notice</b>: Constant WEAVERX_ADMIN_DIR already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>77</b>

    <b>Notice</b>: Constant WEAVERX_SUBTHEMES_DIR already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>78</b>

    <b>Notice</b>: Constant WEAVERX_STYLE_FILE already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>79</b>

    <b>Notice</b>: Constant WEAVERX_MINIFY already defined in <b>/home/sites/6b/b/ba4609c25b/public_html/wp-content/themes/weaver-xtreme/settings.php</b> on line <b>81</b>

    #59297

    Weaver
    Keymaster

    Sorry, I tried to move your post a couple of days ago to the correct forum, but it ended up lost.

    I can’t explain what is going on. Do you use a child theme?

    You are somehow getting a double loading of some theme files. I would try to uninstall Weaver Xtreme, and then reinstall in.

    I’ve never seen this symptom before.

    #59299

    orbitcreative
    Participant

    Thanks for getting back to me.

    I haven’t used a child theme, but i will uninstall the files and try again. It could be a quirk with the plugin, but PaymentSense are adamant there isn’t a problem. Other payment gateway plugins work fine.

    #59347

    alex333
    Participant

    As per the concept of WordPress (and respectively WooCommerce), a file requested with the locate_template WordPress function (and respectively the wc_locate_template WooCommerce function) and found in a theme directory is considered as a template.

    Based on that, on the request made by the Paymentsense plugin for the settings.php template, WordPress retrieves the settings.php file found into the Weaver Xtreme theme directory which results into improper theming (replacement) of the settings.php template of the Paymentsense plugin with the Weaver Xtreme theme settings file.

    A possible fix of this would be renaming the settings.php file found in the Weaver Xtreme directory with a non-conflicting (non-generic) file name, e.g. weaver-settings.php and change the reference to it at line 558 on the functions.php file from:

    require_once( get_template_directory() . ‘/settings.php’ );

    to:

    require_once( get_template_directory() . ‘/weaver-settings.php’ );

    #59350

    scrambler
    Moderator

    @weaver will need to comment on that

    #59354

    Weaver
    Keymaster

    It is faulty logic on the part of the plugin.

    There can be all sorts of different files contained in the main theme directory. As far as I know, there is no general WP naming convention for a “settings.php” file, therefore no one should assume anything about such a file. It is a perfectly valid file for any theme to use, but not any file a plugin should assume has some specific meaning.

    I see not need to change the already compliant file in Weaver Xtreme. I consider this a pluign problem, and the change belongs there. Note that when the Woocommerce plugin used the function to load a template, those templates are prefixed with “wc_”, which is the proper practice.

    #59359

    alex333
    Participant

    Right, there is no naming convention for the name of the templates, neither the suggestion given for using the prefix “wc_” is part of such a naming convention or official recommendation. I am not intending to advocate or blame neither the plugin, neither the theme, neither the way how the WordPress templates work. I am just suggesting a possible fix that I believe is conflict-free and solves the issue.

    #59370

    Weaver
    Keymaster

    By convention, plugins are supposed to work with all themes. It is really up to plugins to not break for some themes (there are some exceptions, but not in this case.) Since themes are reviewed by WordPress.org to ensure they meet specific theme design requirements, while plugins receive only minimal review, the burden is really on plugins. There are far more plugins than themes, and the task to make a theme compatible with all plugins would be impossible.

    Many themes do have special support for some plugins – Woocommerce and Yoast SEO are two great examples. But neither of those are incompatible with themes in the repository – they just get special support by some themes.

    #59423

    orbitcreative
    Participant

    Thanks to everyone for their input on this matter. By way of update i have mentioned the above comments to PaymentSense and they are looking into steps to resolve this issue with their next plugin update. I will keep you updated. Once again, many thanks.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.