photocurio

Matt,
I’m using the latest versions: 3.1.1 ACF FontAwesome, 5.8.7 ACF Pro.

If I check “turn on the pro icons”, I have all icons available in the ACF fontawesome field, no matter what icons I have selected in the field definition. I do want the pro icons. I just don’t want every font weight, and I don’t want the brands icons.

Updating and re-saving the field doesn’t make any difference.

• This reply was modified 4 years, 8 months ago by photocurio.

It doesn’t seem to work. I have limited fonts (i.e. no brands) selected in my field definition, but in the admin I do see the brands when I am selecting an icon.

(I wish I could upload screenshots)

Actually I basically have this. dg_query isn’t needed. I did it this way:

function dg_icon_template($icon, $description, $id) {
    $internal = get_field('internal', $id) ? 'internal' : 'external';
    $icon = '<li class="%class% ' . $internal . '"><a href="%link%" target="_blank">%title%</a>&mdash; %date%</li>';
    return $icon;
}
add_filter('dg_icon_template', 'dg_icon_template', 10, 3);

I would still like to know how to add the class to %class%, instead of declaring a new variable.

@stodorovic any update on this request?

Sweet! Resetting ‘plugin_options_db_version’ worked. I appreciate the support!

Thanks Tobias. These capabilities don’t show in User Role Editor. I’ll have to write a function, and put it in my themes I guess.

It would be nice if the plugin had an option to give access to editors.

Matt, these are the plugins that I use that have network level settings:
Updraftplus Backups
User Role Editor
WP Super Cache
WP Migrate Pro
Breadcrumb NavXT

Something like this on your front page template will work. The idea is that you have a loop to fetch all blogs, and inside that loop there is another loop that gets the posts from each blog. I wouldn’t try this on a large network!

<?php
  // get all blogs
  $blogs = get_sites();
  if ( 0 < count( $blogs ) ) :
?>
<h3>Microsites hosted on this network:</h3>
<?php foreach( $blogs as $blog) :
if (1 == $blog->blog_id) continue;
switch_to_blog( $blog->blog_id );

$description  = get_bloginfo( 'description' );
$blog_details = get_blog_details( $blog->blog_id );
$posts = get_posts(); ?>

<div class="blog">
  <h3>
    <a href="<?= $blog_details->path ?>"><?= $blog_details->blogname ?></a>
  </h3>
  <?= $description ?>
  <ul>
  <?php foreach ($posts as $post) : ?>
  <li><?= $post->post_title ?></li>
  <?php endforeach; ?>
  </ul>
</div>

<?php endforeach; ?>
<?php endif;
switch_to_blog(1); ?>

P.S. I found the constants in the wp_blogs table, and they seem to be correct. All my blogs have a site_id of 1, and the root site has a blog_id of 1.

I had the same issue. Saving my WP Site Sync settings fixed it.

I’m not really an htaccess expert, but think I see why the above rules won’t work: the WordPress rules have already processed the request before they execute. Your rewrite rules need to go inside the WordPress block. Put them between RewriteBase and the rule for index.php.

This is how I put in my hard-coded rewrite rules:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /

# GONE
RewriteRule ^typo3temp\/(.*)$ - [G,L]
RewriteRule ^idc\/(.*)$ - [G,L]
RewriteRule ^fusa\/(.*)$ - [G,L]
RewriteRule ^fileadmin\/(.*)$ - [G,L]

# FORBIDDEN
RewriteRule ^\.well-known\/(.*)$ - [F,L]
RewriteRule ^browserconfig.xml - [F,L]

RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

• This reply was modified 6 years, 6 months ago by photocurio.
• This reply was modified 6 years, 6 months ago by photocurio.

I can confirm this error. Please fix!

I’m having this problem also. None of the sites on our Windows server are sending email right now. The used to work. Yesterday mail was going out.

I’ve been told these are warnings, not errors. And although the whitescreen made me think it broke my site, niether the site nor the admin was actually broken. Just the page /wp-admin/options.php was broken.

Anyway, the developers provided me with a fix, and testing shows no more php warnings, and no whitescreen. Nice! I assume this fix will be in the next release of the plugin.

p.s. I should add that I get a whitescreen with these errors.

• This reply was modified 6 years, 11 months ago by photocurio.