Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • This error may or may not be due to WPInvoicing plugin. We need to troubleshoot for that. First of all, can you let me know if your site is directly accessible to users or you have some HTTP authentication enabled? If the HTTP authentication is enabled on your site then this error will come as loopback request from health check plugin will fail.

    Please let me know admin details and FTP details in private reply to troubleshoot more for your site.

    Source link:
    https://wpinvoicing.com/support/topic/a-plugin-has-prevented-updates-by-disabling-wp_version_check/
    https://www.icrowdresearch.com
    https://www.abrightclearweb.com/the-wordpress-site-health-check-help-or-hindrance/

    There are several solutions to this issue. Please see the bulleted list below.

    First make sure that mod_rewrite is installed and enabled on your Apache II web server, and also make sure that the webserver allows your .htaccess file to override the server directory configuration.
    Make sure that your WordPress .htaccess file is present in your WordPress installation. If it is not, simply create a blank file called .htaccess and upload it to your WordPress installation folder.

    Set permissions on your .htaccess file that allows your web server to write to the file – CHMOD 666.
    Go back and set your permalinks option to the “default” option and save the change. Then, set it to something other than the default and save the change.

    If your .htaccess file is writeable by the web server, it will contain new directives that sets rewrite rules for your custom permalink option.
    If it is not writeable, you will see a message below your permalinks screen that contains the rule set you need to add manually into your .htaccess file, save it, and upload it back to the WordPress installation folder.

    Check to see if you can navigate from your front page menu links without error.
    If the issue persists, contact your web host support team for further assistance.

    Source Link: https://theme-fusion.com/documentation/avada/technical/custom-permalinks-return-404-errors/
    https://www.icrowdresearch.com
    https://www.ads-software.com/support/topic-tag/server-error/

    Fixing errors when uploading images in WordPress

    The following documentations reviews the most common problems occurring when uploading images in WordPress, and provides solutions for them :

    Image filename

    HTTP Error When Uploading Image
    Unable to create directory and broken images in the Media Library
    File exceeds the upload_max_filesize
    Check your image file name
    The first thing to check is the name of the image. If the file name contains any special character (like a semi-colon or an equals sign etc) it might not be uploaded.

    HTTP Error When Uploading Image

    This happens when you are trying to upload an image that is large in pixel size, for example, an image with 3000 x 2000 pixel. Which is too large for your server to process.
    we will research and analysis Some server shows error even when your image is less than 3000 x 2000 pixel, it all depends on your server resources.

    Source Link:
    https://docs.presscustomizr.com/article/229-fixing-errors-when-uploading-images-in-wordpress
    https://www.hostinger.com/tutorials/http-error-when-uploading-images-to-wordpress

    use this code to solve your error

    The simplest way to filter items is with selectors, like classes. For example, each item element can have several identifying classes and Research Report factores: transition, metal, lanthanoid, alkali, etc.

    <div class=”grid”>
    <div class=”element-item transition metal”>…</div>
    <div class=”element-item post-transition metal”>…</div>
    <div class=”element-item alkali metal”>…</div>
    <div class=”element-item transition metal”>…</div>
    <div class=”element-item lanthanoid metal inner-transition”>…</div>
    <div class=”element-item halogen nonmetal”>…</div>
    <div class=”element-item alkaline-earth metal”>…</div>

    </div>
    Set a selector with the filter option. Items that match the selector will be shown. Items that do not match will be hidden.

    // filter .metal items
    $grid.isotope({ filter: ‘.metal’ });

    // filter .alkali OR .alkaline-earth items
    $grid.isotope({ filter: ‘.alkali, .alkaline-earth’ });

    // filter .metal AND .transition items
    $grid.isotope({ filter: ‘.metal.transition’ });

    // show all items
    $grid.isotope({ filter: ‘*’ });

    Source link: https://isotope.metafizzy.co/filtering.html

    https://github.com/metafizzy/isotope/issues/724

    first, thank you many times over for taking the time to file a bug. For the report to be most effective, we’ve noticed the following characteristics help us get to a solution the fastest.

    Note that bug Research reports should only be submitted for existing functionality that does not work as intended. If you came here to submit a feature request or discussion topic, head on to
    TL;DR example issue
    Title: Signal messages jiggle in the conversation list
    I have searched open and closed issues for duplicates
    I am submitting a bug report for existing functionality that does not work as intended
    I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
    This isn’t a feature request or a discussion topic
    Bug description
    Every time there’s a food commercial my messages start jiggling.

    Steps to reproduce
    Open Signal
    Go to the main conversation list
    A commercial about food comes on the television in the other room
    Actual result: Signal messages start to jiggle in the conversation list for a couple seconds.

    Expected result: Nothing should happen. Messages should just stay as they are.

    Screenshots
    signal jiggle

    Device info
    Device: LG Nexus 4

    Android version: stock Android 5.1.1

    Signal version: 3.15.0

    App state
    Signal messages and calls registered, SMS disabled, passphrase enabled

    Link to debug log
    https://debuglogs.org/2488708be425d005221703ff268214942480a2b4a7b856f30a63326b803144d1

    Characteristics
    Search, search, search
    Before submitting a new issue please search if someone has already opened an issue about the same topic. Don’t forget to search for both open and closed issues as GitHub only searches for open issues by default. (You may also wish to check out GitHub’s help article about search to get more accurate results.)

    Come up with a concise and descriptive title
    A good title summarizes the issue in a few words and makes it easily searchable. There’s no need to use tags such as “[Feature]” in the titles. Speaking of search: Did you try searching duplicate issues by using your title as search keywords?

    Try to reproduce the bug
    The developers need to see the bug in order to fix it. Try to find the exact conditions and steps that trigger the bug and add them to your issue report. Ideally, the developers can follow your steps and recreate the bug on their own device.

    Capture a debug log
    The debug log describes what Signal was doing while it was running. If you capture a debug log immediately after a bug occurs, the developers can use the log to see exactly what was going on in your installation of Signal. Even in the case where you know the exact steps that cause the bug on your device, that doesn’t guarantee that the same steps will cause the bug on the developer’s device. It is always helpful to add a debug log to your issue report.

    How to capture a debug log

    Immediately after the bug has happened go to Signal Settings -> Advanced -> Submit debug log
    Tap Submit to generate a URL link for the log
    Copy the link and paste it in your issue report
    Note: If you are using a passphrase and the bug appears before you can successfully unlock the app, you can capture a debug log directly via the menu in the passphrase screen. You can also capture debug logs with adb if you cannot access any of Signal’s debug log menus.

    Debug log privacy

    Debug logs captured within Signal are stripped of personal information. However, please note that the last two digits of phone numbers may be visible in the logs (e.g. +1 555 867 5309 will show as +*********09). This is to help differentiate between contacts when analyzing a log.

    Add a screenshot
    Sometimes a picture is worth a thousand lines of debug logs, but this doesn’t mean that you shouldn’t add a debug log too :). If the problem is visual and difficult to describe, a screenshot can go a long way. Different Android vendors have different ways of taking screenshots. Please check how to do it on your specific device. Usually it’s a combination of pressing the volume buttons and power button at the same time.

    You may need to toggle the Screen security option in Signal’s Privacy settings before taking a screenshot.

    Device and app information
    What’s your device?
    What Android version is it running?
    What version of Signal do you have?
    App state
    What are the relevant preferences that you have set that may be related to the issue? Some examples:
    Registration state for Signal messages and calls
    MMS settings
    Passphrase
    Theme
    Message trimming
    If this is a bug involving a second party, what’s their device/app info and app state?
    Finished!
    Congratulations! You are done. You have achieved the badge: Creator of Glorious Bug Reports!:sparkles:

    Now you can submit your report. Thanks for your help!

    Advanced capturing
    Here are some advanced ways to get more information from your device.

    Debug logs with adb
    adb logcat
    Capturing raw log data with adb may expose private information like phone numbers. Please review your adb debug logs before submission.

    Screenshots with adb
    adb shell /system/bin/screencap -p /sdcard/screencap.png && adb pull /sdcard/screencap.png
    Video (only for Android 4.4 and up)
    A small video or gif can be helpful if the problem is visual and difficult to describe.

    adb shell screenrecord /sdcard/screenrecord.mp4
    Then pull it from the device.

    adb pull /sdcard/screenrecord.mp4
    Animated gifs
    If you have ffmpeg and imagemagick, you can quickly convert a video into an animated gif:

    ffmpeg -i screenrecord.mp4 -r 10 screenrecord%05d.png
    convert screenrecord*.png screenrecord.gif
    rm screenrecord*.png
    Manually making an Animated gif
    mkdir tmpScreens
    cd tmpScreens
    # perform as many screenshots as you need to string together the animated gif:
    adb shell screencap -p | perl -pe “s/\x0D\x0A/\x0A/g” > adb-screenshot-date +%s.png
    convert -delay 70 -loop 0 adb-screenshot-*.png anim.gif
    Source link:
    https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
    https://elm-lang.org/news/the-perfect-bug-report

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