• Hi,

    I created a website on a local server and I used WP Data Access to show a database table on a private page in a frontend dashboard using [wpdadiehard project_id=”1″ page_id=”1″]. The table shows up, but as soon as I click on something like edit or show an entry I get a 403 error page. I can also not browse to the second page or use the search function. On my local server everything worked fine. I didn’t change anything, just migrated the whole website to the online server.

    What could be wrong here?
    The website is still not live, as it is under development, so I cannot provide a link. I hope somebody can point in the right direction.

    Thanks a lot!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    Hi @webnicole,

    Is this shortcode running on the homepage? If so, please try to use it on a sub page. There is no guarantee, but it often works.

    Please let me know,
    Peter

    Thread Starter webnicole

    (@webnicole)

    Hi Peter,

    no, it’s not on the homepage.
    Also, I had problems updating the plugin today, again related to permissions. So, just to make sure that nothing broke during migration from the local server, I deleted the plugin, installed it fresh and created a new project. Sadly, there is the same problem. The table is displayed on the sub page, but I cannot view or edit the entries or perform a search on the table.
    Why is it not working now when it was okay on the local server? Do you have any idea what could be wrong here? I can also contact the server admin, could there be a problem with the server configuration?

    Thanks!

    Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    Hi @webnicole,

    Sorry to hear! Unfortunately shortcode wpdadiehard does not work with every theme. Not sure if the premium version is an option for you? The premium version allows to run your Data Project as an AngularJS app. That shortcode works with every theme. You can find a demo and documentation about Data Forms here:
    https://wpdataaccess.com/docs/documentation/data-forms/project-demo/

    Hope this helps,
    Peter

    Thread Starter webnicole

    (@webnicole)

    Hi Peter,

    the theme is not the problem, I had the same theme installed on my local server, and it worked. But I contacted the server admin and asked him to check the error logs. He replied that any activity on this page is blocked because of a security issue:

    COMODO WAF: Blind SQL Injection Attack||my-domain.com|F|2″] [data “Matched Data: table_name found within ARGS_NAMES:table_name: table_name”] [severity “CRITICAL”]

    The URL of the page is like: https://my-domain.com/…/?table_name=my_table

    He asked me to contact you and see if there is a solution.
    What can I do?

    Thanks a lot!

    Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    Hi @webnicole,

    A blind attack? Or a blind block? 🙂

    The plugin uses the table_name argument in many requests. So far I never had any modsecurity issues with the table_name argument. I hope CWAF remains an exception.

    There are two simple solutions:
    (1) Update to premium and use Data Forms
    (2) Ask your server admin to add a modsecurity rule

    A third solution would be to rename the table_name parameter, which means changing the majority of the plugin source code files. This takes a lot time and introduces the risk of missed changes and code that no longer works.

    BTW, are you able to use the Data Publisher on your website? I wonder as the same argument is used for publications as well.

    Best regards,
    Peter

    Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    Hi @webnicole,

    Is this issue still open? You might try to update to 4.2.7 and test again. The third solution I mentioned earlier seemed to be simpler than extpected. I dare not to do any promises, but I hope shortcode wpdadiehard now works with “any” theme. Can you give it a try and let me know?

    Thanks,
    Peter

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘403 error in frontend’ is closed to new replies.