288

[Admin]

In reply to: Using categories from Events Manager plugin in Graphene slider

#31606

Marking thread as resolved. You can do this yourself as well.

[Admin]

In reply to: Warning: sprintf() [function.sprintf]: Too few arguments in

#31602

Please join the discussion about this issue in the other similar topic so that we can keep track of things better:

https://forum.graphene-theme.com/graphene-support/php-sprintf-warning/page/3

I’m closing this topic.

[Admin]

In reply to: Theme Error: Memory exhausted

#31588

Quote:

Yes i have 609 post. so this is kind of bug or some coding error whit the 1.8 version?

It’s not a bug, neither is it a coding error. Just an unforeseen consequence.

Quote:

So this version should make the post and page to load match faster?

It reduces the number of database query, so yes it will (in theory) make your posts and pages load teeny tiny bit faster. Database queries are typically very fast (in order of milliseconds), so there won’t be much difference. But it’s always good practice to not use any more resources than you need.

[Admin]

In reply to: Widgets and Menu Not Working

#31411

For menu, you’ll see that there are two new menu locations specific for the mobile theme. There’s no mobile-specific setting for widgets though (not yet, at least).

[Admin]

In reply to: Theme Error: Memory exhausted

#31586

Version 1.8 uses a new structure in saving the theme’s custom fields for each posts and pages (post-specific options like slider image, date display, etc.). This new structure reduces the number of database query for each post.

However, to avoid resetting all the post-specific options that you may have set prior to version 1.8, the old structure needs to be updated to the new structure. That’s what the graphene_convert_meta() function is for.

The problem was that the function attempts to update the structure for all posts and pages at one go, so if you have a lot of posts and pages, it’s not unlikely that the memory usage spikes and hence you get that memory exhausted error. This was supposed to be a one-off thing, so I wasn’t expecting that memory spike to be a problem in terms of performance.

In any case, this will be changed in version 1.8.1, where the function will update the theme’s custom fields structure for each post as the custom fields for that particular post are requested. This should get rid of the memory spike while still updating the old structure to the new one so you won’t lose your post- and page-specific settings.

[Admin]

In reply to: Theme Error: Memory exhausted

#31584

Quote:

I dont find that files.

The file is in the Graphene theme’s folder.

[Admin]

In reply to: Edit Header Text Properties

#31617

The CSS code that the theme generates to affect the header text was overridden by another piece of code in the theme’s style.css. The updated code simply made it so that the generated CSS code has higher priority.

[Admin]

In reply to: Creating child theme in 1.8 causes loss of column widths

#31523

Try using this updated package:

http://graphene.googlecode.com/files/graphene-1.8r448.zip

[Admin]

In reply to: Theme Error: Memory exhausted

#31582

Update first, then edit the admin/db-updater.php file to remove that line. Try and let me know if you’re still getting memory exhausted error.

[Admin]

In reply to: PHP SPrintf Warning

#31303

OK, try replacing includes/theme-head.php with the updated one here:

http://graphene.googlecode.com/svn/trunk/graphene/includes/theme-head.php