Forum Replies Created
-
Posts
-
Ok, are these your standard answers? First you recommend to raise the memory limit, which does not work because of a hard-coded limit in the code. And if that does not work you tell me to get some paid customization?
I think it does not require a lot of code! It just needs to make 2 post_type non-public instead of one, so it is just a question of the right syntax in one line of code, which might be really easy for the developer of this code.If I simply replace ‘attachments’ with our post_type, it works.
I would just have both to be not “public” to keep the linkpicker as clean as possible. The existance of the array with “allowed post types” makes me think that the developer was thinking of the possibility of adding some more!?How can I add another post type here NOT to be a public:
/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/generic-helper.class.php
line 256$post_types = get_post_types(array('public' => false, 'name' => 'attachment', 'show_ui'=>false, 'publicly_queryable'=>false), 'names', 'NOT');??
Hi.
Unfortunately our chief of development would not like anyone else to have an admin access to our development site, so we have to solve this somehow differently, sorry.
BUT:
I got an idea, where our problem is. The hard-coded setting of the memory limit, mentioned above, is inside the function generating the “linkpicker”. We have have a database table wp_term_taxonomy with more than 50,000 entries already and they are all written in an array to build the linkpicker.
There is a different code defining the allowed post types and taxonomies:
/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/generic-helper.class.php line 288:
$taxonomies = apply_filters(‘avia_public_taxonomies’, $taxonomies);
How can I exclude some taxonomies types from this filter??
Kind regardsHi,
i just found out that enfold is limiting the memory use itself to 256MB, so changing the PHP and WP limit to a higher value does not work.
/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/html-helper.class.php
line 745://necessary for installations with thousands of posts @ini_set("memory_limit","256M");This can be closed. I solved it like this:
$this->loop[$key]['content'] = !empty($entry->post_content) ? $entry->post_content : $entry->post_excerpt;Thanks again.
Hi, thanks for your quick answer. I was expecting this, but I am not really happy with the solution. WHY is this tiny modal window taking up so much memory?? Why would it work with other content elements. If our media library grows (it will), we will get the error again, even with GBs of memory!?
I think there must be some loop in the avia framework somewhere checking ALL attachments at once? Possible?
Kind regards
