Sunny Ratilal

I’ve fixed the bug and it will be released in EDD 2.6.14.

Hi Tijmen,

I’ve confirmed the bug and will issue a bug fix in the next release of EDD. Thanks for bringing this to our attention.

You’d need PHP knowledge to accomplish this.

Use the get_children function for the parent page and loop through the returned results.

But if you’re doing all of this from the Post Editor then you need to create a custom shortcode for this to work. Something like this plugin could also work in conjunction with the get_children function https://www.ads-software.com/plugins/php-code-for-posts/.

I’d recommend looking at the examples for the get_children function to get an idea of how to loop through the posts correctly.

Try changing to the default WordPress theme and disabling plugins one-by-one and seeing if the error is fixed when you make any of those changes.

You can use the get_children function along with wp_get_post_parent_id to list all the sub-pages in that parent post type.

I’d recommend using something like Chrome Developer Tools to check what the actual link of the images are and then check if they exist at the directory on the server.

It could also be that the directory your images are stored are protected and not accessible due to the way permissions are configured. Unlikely, but a possibility.

Best way to do it would be separate the listing via pages (i.e. 100 listings per page or so). Trying to load all 60,000 on one page would cause your website to crash and the connection may even time out.

This is most likely configurable by the Theme Options as the theme developer has either hardcoded it into the theme or it’s configurable by a Settings page in the WordPress admin

You can use the wpdb class which handles all communication with MySQL.

It looks like custom code has altered the login URL somewhere along the line.

Could you try with the default WordPress theme and see if that fixes the issue?

This could be due to the way the pages are configured under Settings > Reading.

You need a page configured for Front page and Posts page.

Looks like there’s an issue with the installation. That file isn’t part of WordPress. Perhaps try reinstalling WordPress?

Hi,

You’d need to enqueue the dashicons to be used in the frontend.

This snippet of code would do that for you:

function load_dashicons() {
    wp_enqueue_style( 'dashicons' );
}
add_action( 'wp_enqueue_scripts', 'load_dashicons' );

Best to put that into a custom plugin.

Currently that’s the default and only view of posts. One way you could segment the posts is by using more categories/tags and viewing posts like that.

This is most likely due to the theme you’re using or a plugin you’ve recently installed.

I’d try and deactivate plugins one by one and see if you get the intended behaviour back and if that doesn’t work, switch to one of the default WordPress themes and see if that fixes it.

If either a plugin/theme deactivation fixes the problem, you’d need to contact the relevant developer and let them know that there’s a bug in their code.