Forum Replies Created

Viewing 8 replies - 76 through 83 (of 83 total)
  • Thread Starter miquelpontes

    (@miquelpontesgmailcom)

    The images with absolute URLs now imports just fine, Thank you.

    I still have the issue with certain pages with the URL like this:
    https://nostramar.org/marenostrum/buceo/canarias/fuerteventura/index.htm
    that were linked by this URL in the text, but were linked like differently in the breadcrums, like this:
    https://nostramar.org/marenostrum/buceo/canarias/fuerteventura/

    And the result is lots of errors in the importing process and a page with no images at all:
    https://nostramar.org/buceo-2/canarias/fuerteventura/

    The source code for this imported page shows a properly converted absolute URL link, and many others kept as relative to the HTML original page (like bandamed.gif or e.gif):

    <div class="entry-content">
    <p><img src="https://nostramar.org/wp-content/uploads/2013/02/barrasuperior.gif" alt="M@re Nostrum"/></p>
    <p>Fuerteventura, jable y salitre<br/>por José Barrera Artiles<br/>Fotos de Rafael Herrero Massieu<br/>Publicado en la revista SCUBA No30, Enero 1997<p/>
    <img src="../../../imagenes/bandamed.gif"/>
    <p><img src="../../../imagenes/lletres/e.gif"/>l jable, las grandes extensiones de arena blanca, cubre cada uno...

    I don’t know how HTML Import processes original links to a given page, but I guess there’s conflict with those pages that are accessed by name (with “index.htm”) and also could be accessed by path (without “index.htm”). To the original web server they were the same page, but to HTML Import this seems to be a problem.

    When the imported page is not named “index.htm” in the original server, all these images are imported flawlessly.

    Do you think I must disable “breadcrumbs” in the original site so these pages could be properly imported? Or is this a coding problem that could be solved?

    Thanks again for your help and support.

    Thread Starter miquelpontes

    (@miquelpontesgmailcom)

    Ups. I forgot to include the equivalent imported code in the previous question:

    <div id="post-23147" class="post-23147 page type-page status-publish hentry">
    											<h1 class="entry-title">Annie Unland</h1>
    
    					<div class="entry-content">
    						<p><img src="https://marenostrum.org/imagenes/barrasuperior.gif" alt="M@re Nostrum"/></p>
    <p>  		  			  		          Annie Unland
    <p><img src="../../../imagenes/bandamed.gif"/>      </p>
    <p><img src="Foto1_Desierto-Tunez.jpg"/>En el desierto de Túnez</p>
    <p>        Hola,
    </p>
    <p>        Me llamo...

    You may observe no translation has been performed. After further studying the case I see there are other pages with the images properly imported, images and all. Why this difference? Pages correctly imported are pretty similar to those that are not properly imported.

    I have also observed that original pages have a folder hierarchy, but this is not completely respected during the import process (most of times it is, but not always), I see pages that lack the last hierarchy level:
    A page that after importing should be at
    https://nostramar.org/acerca-de/colaboradores/aunland/
    I found it to be imported at
    https://nostramar.org/colaboradores/aunland/
    so it must be manually adjusted, not a real problem.

    Thanks a lot (and excuse me for my English, which is not as good as it should be).

    miquelpontes

    (@miquelpontesgmailcom)

    Amets, then try uploading the old version of the plugin from the backup, that should work too without tinkering with the code.

    If you don’t have a backup or a copy of the older version of the plugin, you can always comment the code in the file, or even delete the wp-filebase plugin folder to recover your site. Good luck.

    miquelpontes

    (@miquelpontesgmailcom)

    I solved it by editing the file /wp-content/plugins/wp-filebase/wp-filebase.php (accessing it via FTP) and changing the original line 33:

    if(func_num_args() > 1)
    	return array_map(__FUNCTION__, func_get_args());

    by the following:

    if(func_num_args() > 1) {
    	$arg_list = func_get_args();
    	return array_map(__FUNCTION__, $arg_list);
    	}

    That worked for me.

    miquelpontes

    (@miquelpontesgmailcom)

    I solved it by editing the file /wp-content/plugins/wp-filebase/wp-filebase.php (accessing it via FTP) and changing the original line 33:

    if(func_num_args() > 1)
    	return array_map(__FUNCTION__, func_get_args());

    by the following:

    if(func_num_args() > 1) {
    	$arg_list = func_get_args();
    	return array_map(__FUNCTION__, $arg_list);
    	}

    That worked for me.

    miquelpontes

    (@miquelpontesgmailcom)

    I solved it by editing the file /wp-content/plugins/wp-filebase/wp-filebase.php (accessing it via FTP) and changing the original line 33:

    if(func_num_args() > 1)
    	return array_map(__FUNCTION__, func_get_args());

    by the following:

    if(func_num_args() > 1) {
    	$arg_list = func_get_args();
    	return array_map(__FUNCTION__, $arg_list);
    	}

    That worked for me.

    miquelpontes

    (@miquelpontesgmailcom)

    I solved it by editing the file /wp-content/plugins/wp-filebase/wp-filebase.php (accessing it via FTP) and changing the original line 33:

    if(func_num_args() > 1)
    	return array_map(__FUNCTION__, func_get_args());

    by the following:

    if(func_num_args() > 1) {
    	$arg_list = func_get_args();
    	return array_map(__FUNCTION__, $arg_list);
    	}

    That worked for me.

    miquelpontes

    (@miquelpontesgmailcom)

    I solved it by editing the file /wp-content/plugins/wp-filebase/wp-filebase.php (accessing it via FTP) and changing the original line 33:

    if(func_num_args() > 1)
    	return array_map(__FUNCTION__, func_get_args());

    by the following:

    if(func_num_args() > 1) {
    	$arg_list = func_get_args();
    	return array_map(__FUNCTION__, $arg_list);
    	}

    That worked for me.

Viewing 8 replies - 76 through 83 (of 83 total)