Forum Replies Created

Viewing 15 replies - 316 through 330 (of 470 total)
  • Thread Starter Abigailm

    (@abigailm)

    Thank you for your very prompt reply –I was thinking it was probably something along those lines. I’ve been using Pods for awhile but have just only gotten started working with relationship fields — so still working my way up the learning curve.

    I also appreciate your creating the bug report because it was the presence of that taggable option that led me astray.

    No need to be rude to the theme author.

    In any theme, display is going to be governed by the style sheet – and without being able to look at your site, it’s difficult for anyone to help you.

    You said that you tried changing the stylesheet — have you tried adding an “!important” directive to the stylesheet?

    If that doesn’t work – can you post the source code for the table here? You don’t have to post any private information — its just necessary to see the html and specific classes that set up the table – so just the first few lines of code for <table> & <tr> should do. If the table is wrapped in a <div> it would help to include that as well.

    Note that this is the same issue reported in this thread: https://wordpress.org/support/topic/php-warning-with-7-1-groups_post_accessposts_where/

    Thank you for posting here Joost. (I appreciate the heads up to a potential security issue)

    Despite similar advance reports from PHP compatibility checkers, I am running the Cloudflare plugin on multiple sites with PHP 7 and PHP 7.1 without any problem or any error messages being logged. So you might want to test on your own.

    I am on a different hosting platform, however, so cannot comment on WPEngine specific issues.

    I am running PHP 7 without any problems.

    I tried PHP 7.1 and the program worked without any particular issues, but the logs showed an error message that I reported here: https://wordpress.org/support/topic/php-7-compatibility-111/

    Have you tried this plugin? https://wordpress.org/plugins/speed-contact-bar/

    (I haven’t tested it so I don’t know whether it is compatible with Evolve or not… but if it does work, then it looks like an easy way to get the feature you are looking for)

    • This reply was modified 9 years, 4 months ago by Abigailm.

    Just another user here — I don’t know what the default or expected behavior of the Groups plugin is, but there is another free plugin that lets you control redirects.

    It’s called Groups 404 Redirect and is available here:
    https://wordpress.org/plugins/groups-404-redirect/

    This also allows you to redirect to a page that you create Groups has a shortcode for login in that you can put in a page – [groups_login] — so with that plugin you can create a more attractive login page (matching your theme) rather than the standard wordpress log in.

    I found this plugin to be very quick to install and set up. Combined with other shortcodes you can create a login page that displays different messages to different groups after they login, simply by placing group-specific content with appropriate short code tags — so your Board Members would see a different greeting page after logging in than the Museum Guides. (I’d note that you have a very attractive site!)

    • This reply was modified 9 years, 4 months ago by Abigailm.
    Thread Starter Abigailm

    (@abigailm)

    Thank you. I am 100% certain that this is a problem on PayPal’s end, but there is no particular need for logging other than for debugging purposes — so it makes sense to have an option to disable. Probably 95% of users never look at the logs.

    Thread Starter Abigailm

    (@abigailm)

    I don’t have a clue either, but I know that his is a very common error for PHP 7.1 (for many themes and plugins). If you Google the error you’ll find many reports.

    One suggestion on how to fix is by prefixing the render call with an @ (Suggested at https://github.com/dompdf/dompdf/issues/1323) I know that worked for a different plugin on the site with a similar issue, but I don’t know if that would work in all cases.

    I rolled back to PHP 7.0 on the site where I am reporting it, so no ongoing issue.

    I just wanted to report it because going forward, you can probably expect more widespread adoption of PHP 7.1 — and I am just letting developers know when I spot an issue that doesn’t seem to be reported previously. So you probably will want to test everything on PHP 7.1 going forward (as well as PHP 7.0 and PHP 5.6)

    I’ve been a web developer for 21 years… so I definitely understand the frustrations when platform and framework upgrades mess up your coding. You work for hours upon hours to get something working correctly, and then the powers that be come along and decide to deprecate some bit of code you are relying on.

    @kawaeh — like you, I was trying to help, by reporting a problem & making a suggestion.
    I also agree with you concerning your comment about bug reporting.

    @kaweah– I want to let you know that I had the exact same problem you report with the support form at the plugin web site that you report several weeks ago (” because their support form won’t accept any failure reports from me. It insists that I haven’t read a plugin conflict page which I know I have read.”)

    In my case, I had posted messages here that were specifically quoting from and asking questions about text from the troubleshooting and FAQ pages that were referenced in the error message. And I got the same rude and argumentative response to my reporting that as you.

    The plugin itself is excellent, but the support system is inexcusably difficult and confusing.

    I’m just posting here so you know that despite their claims, you are not the only one who has experienced this issue. When you report a problem, you get an argument.

    Thread Starter Abigailm

    (@abigailm)

    Thank you –one suggestion I have would be a way for the administrator to preview and navigate pages as it would appear to different groups.

    I have a plugin called “User Switching” – https://wordpress.org/plugins/user-switching/ – that in the past allowed me to do just that. I could just select a user in a particular group and switch to take on that user’s role.

    However, with the upgrade to v. 2.00/2.01 that no longer works. When I switch, the site slows down and pages won’t load. I don’t get any particular error message showing in logs, but I suspect that there is a problem with cookies and perhaps some sort of infinite loop being created within the Groups plugin.

    I didn’t report this before as it is clearly a conflict with another plugin rather than a problem with the Groups. But it would be a nice feature for Groups (though probably not all that easy to code… so this is only a suggestion, not an expectation).

    Colin, you might find Kento’s answers to my report of similar problems helpful, here:
    https://wordpress.org/support/topic/problems-with-upgrade-to-version-2-00/

    I understand your frustration as I experienced similar issues with a site where it is important for most pages to be protected from public access. As someone who also manages multiple sites, I also know how frustrating it is to discover a problem that impacts use or security of multiple sites at once.

    However, I think it is unfair to blame the plugin offer for problems caused to your reputation. This plugin was clearly a major upgrade (from version 1.13 to 2.0) – and the changelog clearly documented this shift in the access restriction model, as well as the legacy mode option.

    Any update to a plugin or theme can cause problems on sites. Sometimes this can be a bug in plugin code, but it can also be due to an unanticipated conflict with other plugins. Because the Groups plugin is particularly critical to site security, I always back up my site before upgrading and test immediately to make sure that the site is functioning as expected. On a high traffic site where security is important, I think it’s also a good precaution to use a maintenance mode system to protect the site from public view during testing.

    Kento responded very quickly to my original report, and a fix was released within 7 hours of my complaint.

    Keep in mind that this is a free plugin!

    Thread Starter Abigailm

    (@abigailm)

    Thank you- you are right, I was looking in the wrong place because of the different location of the field on the “pages” bulk edit page.

    I think I have managed to update all files to the new protocol now.

    I do feel that the direct use of groups to manage page access is an improvement overall and much more intuitive. So thank you for your great work & prompt response to questions and support requests posted here!

Viewing 15 replies - 316 through 330 (of 470 total)